From: Jan Kara <jack@suse.cz>
To: cgxu519 <cgxu519@gmx.com>
Cc: Jan Kara <jack@suse.cz>, jack@suse.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext2: compare old and new mode before setting update_mode flag
Date: Wed, 21 Nov 2018 15:29:50 +0100 [thread overview]
Message-ID: <20181121142950.GE28182@quack2.suse.cz> (raw)
In-Reply-To: <e9db0f67-fc05-9ec8-5953-8e3724c43cc8@gmx.com>
On Wed 21-11-18 18:55:28, cgxu519 wrote:
> On 11/19/18 6:04 PM, Jan Kara wrote:
> > On Sat 17-11-18 17:01:00, Chengguang Xu wrote:
> > > If new mode is the same as old mode we don't have to reset
> > > inode mode in the rest of the code, so compare old and new
> > > mode before setting update_mode flag.
> > >
> > > Signed-off-by: Chengguang Xu <cgxu519@gmx.com>
> > I don't think this is quite correct. E.g. I would think that i_ctime should
> > be updated even if the effective mode resulting from acl did not change.
>
> I think __ext2_set_acl() will probably update i_ctime in this case, am I
> missing something?
Yeah, you're right. But I'd still prefer to keep the code simple as is.
There's no great reason to optimize this since saved time is going to be
minimal and the code is not performance critical.
Honza
> > diff --git a/fs/ext2/acl.c b/fs/ext2/acl.c
> > index cf4c77f8dd08..f4dd728393c8 100644
> > --- a/fs/ext2/acl.c
> > +++ b/fs/ext2/acl.c
> > @@ -226,7 +226,8 @@ ext2_set_acl(struct inode *inode, struct posix_acl *acl, int type)
> > error = posix_acl_update_mode(inode, &mode, &acl);
> > if (error)
> > return error;
> > - update_mode = 1;
> > + if (mode != inode->i_mode)
> > + update_mode = 1;
> > }
> > error = __ext2_set_acl(inode, acl, type);
> > if (!error && update_mode) {
> > --
> > 2.17.2
> >
> >
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2018-11-22 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 9:01 [PATCH] ext2: compare old and new mode before setting update_mode flag Chengguang Xu
2018-11-19 10:04 ` Jan Kara
2018-11-21 10:55 ` cgxu519
2018-11-21 14:29 ` Jan Kara [this message]
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=20181121142950.GE28182@quack2.suse.cz \
--to=jack@suse.cz \
--cc=cgxu519@gmx.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).