From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Seth Forshee <sforshee@kernel.org>, Jeff Mahoney <jeffm@suse.com>,
reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH v2 1/8] fs: don't use IOP_XATTR for posix acls
Date: Tue, 31 Jan 2023 16:18:32 +0100 [thread overview]
Message-ID: <20230131151832.GA30960@lst.de> (raw)
In-Reply-To: <20230131145501.cscah5qujqh4e36k@wittgenstein>
Sorry for not keeping up with your flow of ideas, so chiming in now:
> diff --git a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c
> index c7d1fa526dea..e293eaaed185 100644
> --- a/fs/reiserfs/inode.c
> +++ b/fs/reiserfs/inode.c
> @@ -2090,6 +2090,7 @@ int reiserfs_new_inode(struct reiserfs_transaction_handle *th,
> if (IS_PRIVATE(dir) || dentry == REISERFS_SB(sb)->priv_root) {
> inode->i_flags |= S_PRIVATE;
> inode->i_opflags &= ~IOP_XATTR;
> + inode->i_op = &reiserfs_privdir_inode_operations;
I wonder if there is any way to set this where reiserfs assigns
the other ops.
> +const struct inode_operations reiserfs_privdir_inode_operations = {
> + .create = reiserfs_create,
> + .lookup = reiserfs_lookup,
> + .link = reiserfs_link,
> + .unlink = reiserfs_unlink,
> + .symlink = reiserfs_symlink,
> + .mkdir = reiserfs_mkdir,
> + .rmdir = reiserfs_rmdir,
> + .mknod = reiserfs_mknod,
> + .rename = reiserfs_rename,
> + .setattr = reiserfs_setattr,
> + .permission = reiserfs_permission,
> + .fileattr_get = reiserfs_fileattr_get,
> + .fileattr_set = reiserfs_fileattr_set,
> +};
I suspect many other ops aren't need either, but I really need input
from people that known reiserfs better.
> + if (likely(!is_bad_inode(inode)))
> error = set_posix_acl(mnt_userns, dentry, acl_type, kacl);
> else
> + error = -EIO;
I wonder if the is_bad_inode check should simplify move into
get/set_posix_acl. But otherwise this patch looks good.
next prev parent reply other threads:[~2023-01-31 15:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:41 [PATCH v2 0/8] acl: remove generic posix acl handlers from all xattr handlers Christian Brauner
2023-01-30 16:41 ` Christian Brauner
2023-01-30 16:41 ` [f2fs-dev] " Christian Brauner
2023-01-30 16:41 ` Christian Brauner
2023-01-30 16:41 ` [PATCH v2 1/8] fs: don't use IOP_XATTR for posix acls Christian Brauner
2023-01-30 16:50 ` Christoph Hellwig
2023-01-30 18:09 ` Christian Brauner
2023-01-31 11:36 ` Christian Brauner
2023-01-31 14:55 ` Christian Brauner
2023-01-31 15:18 ` Christoph Hellwig [this message]
2023-01-30 16:41 ` [PATCH v2 2/8] xattr: simplify listxattr helpers Christian Brauner
2023-01-30 16:51 ` Christoph Hellwig
2023-01-30 16:41 ` [PATCH v2 3/8] xattr: add listxattr helper Christian Brauner
2023-01-30 16:51 ` Christoph Hellwig
2023-01-30 16:42 ` [PATCH v2 4/8] xattr: remove unused argument Christian Brauner
2023-01-30 16:42 ` [PATCH v2 5/8] fs: drop unused posix acl handlers Christian Brauner
2023-01-30 16:42 ` [PATCH v2 6/8] fs: simplify ->listxattr() implementation Christian Brauner
2023-01-30 16:42 ` Christian Brauner
2023-01-30 16:42 ` [f2fs-dev] " Christian Brauner
2023-01-30 16:42 ` Christian Brauner
2023-01-30 16:52 ` Christoph Hellwig
2023-01-30 16:52 ` Christoph Hellwig
2023-01-30 16:52 ` [f2fs-dev] " Christoph Hellwig
2023-01-30 16:52 ` Christoph Hellwig
2023-01-30 16:42 ` [PATCH v2 7/8] reiserfs: rework " Christian Brauner
2023-01-30 16:42 ` [PATCH v2 8/8] fs: rename generic posix acl handlers Christian Brauner
2023-01-30 16:53 ` Christoph Hellwig
2023-04-26 23:07 ` [f2fs-dev] [PATCH v2 0/8] acl: remove generic posix acl handlers from all xattr handlers patchwork-bot+f2fs
2023-04-26 23:07 ` patchwork-bot+f2fs
2023-04-26 23:07 ` patchwork-bot+f2fs
2023-04-26 23:07 ` patchwork-bot+f2fs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230131151832.GA30960@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=sforshee@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.