summaryrefslogtreecommitdiff
path: root/drivers/memstick/core
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-01-25 09:15:15 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2023-01-25 09:15:15 -0800
commit7c46948a6e9cf47ed03b0d489fde894ad46f1437 (patch)
tree326920f286b3929648145e83500e384186b69877 /drivers/memstick/core
parent948ef7bb70c4acaf74d87420ea3a1190862d4548 (diff)
parentfacd61053cff100973921d4d45d47cf53c747ec6 (diff)
Merge tag 'fs.fuse.acl.v6.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping
Pull fuse ACL fix from Christian Brauner: "The new posix acl API doesn't depend on the xattr handler infrastructure anymore and instead only relies on the posix acl inode operations. As a result daemons without FUSE_POSIX_ACL are unable to use posix acls like they used to. Fix this by copying what we did for overlayfs during the posix acl api conversion. Make fuse implement a dedicated ->get_inode_acl() method as does overlayfs. Fuse can then also uses this to express different needs for vfs permission checking during lookup and acl based retrieval via the regular system call path. This allows fuse to continue to refuse retrieving posix acls for daemons that don't set FUSE_POSXI_ACL for permission checking while also allowing a fuse server to retrieve it via the usual system calls" * tag 'fs.fuse.acl.v6.2-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping: fuse: fixes after adapting to new posix acl api
Diffstat (limited to 'drivers/memstick/core')
0 files changed, 0 insertions, 0 deletions