From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
David Sterba <dsterba@suse.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] hfs: update comments on hfs_inode_setattr
Date: Wed, 25 Mar 2026 12:52:36 +0100 [thread overview]
Message-ID: <x55spdwyhlsqy5aybokpy6ffmsv2jpyp5kypshv4vt4c3y7tlm@76qv5tqlsibs> (raw)
In-Reply-To: <20260325063711.3298685-2-hch@lst.de>
On Wed 25-03-26 07:36:48, Christoph Hellwig wrote:
> The top of function comment about hfs_inode_setattr is severely out
> of date and reference a previous name for this function. Remove it,
> and update the comments in the file to record the still relevant bits
> directly.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
I agree the comments seem really outdated. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/hfs/inode.c | 21 ++-------------------
> 1 file changed, 2 insertions(+), 19 deletions(-)
>
> diff --git a/fs/hfs/inode.c b/fs/hfs/inode.c
> index 878535db64d6..72948eb2fadc 100644
> --- a/fs/hfs/inode.c
> +++ b/fs/hfs/inode.c
> @@ -622,23 +622,6 @@ static int hfs_file_release(struct inode *inode, struct file *file)
> return 0;
> }
>
> -/*
> - * hfs_notify_change()
> - *
> - * Based very closely on fs/msdos/inode.c by Werner Almesberger
> - *
> - * This is the notify_change() field in the super_operations structure
> - * for HFS file systems. The purpose is to take that changes made to
> - * an inode and apply then in a filesystem-dependent manner. In this
> - * case the process has a few of tasks to do:
> - * 1) prevent changes to the i_uid and i_gid fields.
> - * 2) map file permissions to the closest allowable permissions
> - * 3) Since multiple Linux files can share the same on-disk inode under
> - * HFS (for instance the data and resource forks of a file) a change
> - * to permissions must be applied to all other in-core inodes which
> - * correspond to the same HFS file.
> - */
> -
> int hfs_inode_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> struct iattr *attr)
> {
> @@ -646,8 +629,7 @@ int hfs_inode_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> struct hfs_sb_info *hsb = HFS_SB(inode->i_sb);
> int error;
>
> - error = setattr_prepare(&nop_mnt_idmap, dentry,
> - attr); /* basic permission checks */
> + error = setattr_prepare(&nop_mnt_idmap, dentry, attr);
> if (error)
> return error;
>
> @@ -663,6 +645,7 @@ int hfs_inode_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> return hsb->s_quiet ? 0 : error;
> }
>
> + /* map file permissions to the closest allowable permissions in HFS */
> if (attr->ia_valid & ATTR_MODE) {
> /* Only the 'w' bits can ever change and only all together. */
> if (attr->ia_mode & S_IWUSR)
> --
> 2.47.3
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2026-03-25 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 6:36 trivial ->setattr cleanups Christoph Hellwig
2026-03-25 6:36 ` [PATCH 1/5] hfs: update comments on hfs_inode_setattr Christoph Hellwig
2026-03-25 11:52 ` Jan Kara [this message]
2026-03-25 16:38 ` vdubeyko
2026-03-25 6:36 ` [PATCH 2/5] adfs: rename adfs_notify_change to adfs_setattr Christoph Hellwig
2026-03-25 11:53 ` Jan Kara
2026-03-25 6:36 ` [PATCH 3/5] affs: rename affs_notify_change to affs_setattr Christoph Hellwig
2026-03-25 11:54 ` Jan Kara
2026-03-25 6:36 ` [PATCH 4/5] proc: rename proc_setattr to proc_nochmod_setattr Christoph Hellwig
2026-03-25 11:56 ` Jan Kara
2026-03-25 6:36 ` [PATCH 5/5] proc: rename proc_notify_change to proc_setattr Christoph Hellwig
2026-03-25 12:12 ` Jan Kara
2026-03-26 14:18 ` trivial ->setattr cleanups Christian Brauner
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=x55spdwyhlsqy5aybokpy6ffmsv2jpyp5kypshv4vt4c3y7tlm@76qv5tqlsibs \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox