Displaying 2 results from an estimated 2 matches for "i_opflags".
Did you mean:
i_flags
2023 Jan 30
1
[PATCH 00/12] acl: remove remaining posix acl handlers
...ry limited set of filesystems. For most of them there is no
> dependence on the generic POSIX ACL xattr handler in any way.
>
> In addition, during inode initalization in inode_init_always() the
> registered xattr handlers in sb->s_xattr are used to raise IOP_XATTR in
> inode->i_opflags.
>
> With the incoming removal of the legacy POSIX ACL handlers it is at
> least possible for a filesystem to only implement POSIX ACLs but no
> other xattrs. If that were to happen we would miss to raise IOP_XATTR
> because sb->s_xattr would be NULL. While there currently is no...
2023 Jan 25
2
[PATCH 00/12] acl: remove remaining posix acl handlers
...ns. First, because a few filesystems relied on the ->list() method
of the generic POSIX ACL xattr handlers in their ->listxattr() inode
operation. Second, during inode initalization in inode_init_always() the
registered xattr handlers in sb->s_xattr are used to raise IOP_XATTR in
inode->i_opflags.
With the removal of the legacy POSIX ACL handlers it is at least
possible for a filesystem to only implement POSIX ACLs but no other
xattrs. If that were to happen we would miss to raise IOP_XATTR because
sb->s_xattr would be NULL.
Fix these things and then get rid of the misleading and effec...