diff options
author | Yan, Zheng <zyan@redhat.com> | 2016-03-07 10:34:50 +0800 |
---|---|---|
committer | Ilya Dryomov <idryomov@gmail.com> | 2016-03-25 18:51:55 +0100 |
commit | 315f24088048a51eed341c53be66ea477a3c7d16 (patch) | |
tree | b0947756198ee556f500e2b5dd001104fec003b8 /REPORTING-BUGS | |
parent | 29dccfa5af388916e48a3edc5ac9dc8cc996d9b4 (diff) | |
download | linux-stable-315f24088048a51eed341c53be66ea477a3c7d16.tar.gz linux-stable-315f24088048a51eed341c53be66ea477a3c7d16.tar.bz2 linux-stable-315f24088048a51eed341c53be66ea477a3c7d16.zip |
ceph: fix security xattr deadlock
When security is enabled, security module can call filesystem's
getxattr/setxattr callbacks during d_instantiate(). For cephfs,
d_instantiate() is usually called by MDS' dispatch thread, while
handling MDS reply. If the MDS reply does not include xattrs and
corresponding caps, getxattr/setxattr need to send a new request
to MDS and waits for the reply. This makes MDS' dispatch sleep,
nobody handles later MDS replies.
The fix is make sure lookup/atomic_open reply include xattrs and
corresponding caps. So getxattr can be handled by cached xattrs.
This requires some modification to both MDS and request message.
(Client tells MDS what caps it wants; MDS encodes proper caps in
the reply)
Smack security module may call setxattr during d_instantiate().
Unlike getxattr, we can't force MDS to issue CEPH_CAP_XATTR_EXCL
to us. So just make setxattr return error when called by MDS'
dispatch thread.
Signed-off-by: Yan, Zheng <zyan@redhat.com>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions