tree 63f403e964ca4b9e80eacad844177b416306d9a0
parent a1fbb607340d49f208e90cc0d7bdfff2141cce8d
author Christian Brauner <brauner@kernel.org> 1675257301 +0100
committer Christian Brauner (Microsoft) <brauner@kernel.org> 1678093160 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iHUEABYKAB0WIQRAhzRXHqcMeLMyaSiRxhvAZXjcogUCZAWraAAKCRCRxhvAZXjc
 oqJTAQD+zJx/dRFA0/P4ULmcAEoo3rlT15AQShkroeoZWJ6dgQD7BHqi17hi9iAx
 ntpxeX7Hh6nD5c9CqCcc1A32I+0pigc=
 =6fcf
 -----END PGP SIGNATURE-----

acl: don't depend on IOP_XATTR

All codepaths that don't want to implement POSIX ACLs should simply not
implement the associated inode operations instead of relying on
IOP_XATTR. That's the case for all filesystems today.

For vfs_listxattr() all filesystems that explicitly turn of xattrs for a
given inode all set inode->i_op to a dedicated set of inode operations
that doesn't implement ->listxattr().  We can remove the dependency of
vfs_listxattr() on IOP_XATTR.

Removing this dependency will allow us to decouple POSIX ACLs from
IOP_XATTR and they can still be listed even if no other xattr handlers
are implemented. Otherwise we would have to implement elaborate schemes
to raise IOP_XATTR even if sb->s_xattr is set to NULL.

Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>