From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, ronny.pretzsch@dfs.de, hare@suse.de
Subject: Re: [PATCH] ext2: Do not update mtime of a move directory when parent has not changed
Date: Thu, 9 Apr 2009 21:15:15 +0200 [thread overview]
Message-ID: <20090409191515.GB3886@duck.suse.cz> (raw)
In-Reply-To: <20090409115132.9f7ccaf0.akpm@linux-foundation.org>
On Thu 09-04-09 11:51:32, Andrew Morton wrote:
> On Thu, 9 Apr 2009 20:41:32 +0200
> Jan Kara <jack@suse.cz> wrote:
>
> > If the parent of the moved directory has not changed, there's no real
> > reason to change mtime. Specs doesn't seem to say anything about this
> > particular case and e.g. ext3 does not change mtime in this case.
> > So we become a tiny bit more consistent.
> >
> > Spotted by ronny.pretzsch@dfs.de, initial fix by J__rn Engel <joern@logfs.org>.
> >
> > CC: ronny.pretzsch@dfs.de
> > CC: hare@suse.de
> > Acked-by: J__rn Engel <joern@logfs.org>
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> > fs/ext2/namei.c | 5 ++++-
> > 1 files changed, 4 insertions(+), 1 deletions(-)
> >
> > diff --git a/fs/ext2/namei.c b/fs/ext2/namei.c
> > index 90ea179..556f258 100644
> > --- a/fs/ext2/namei.c
> > +++ b/fs/ext2/namei.c
> > @@ -352,7 +352,10 @@ static int ext2_rename (struct inode * old_dir, struct dentry * old_dentry,
> > inode_dec_link_count(old_inode);
> >
> > if (dir_de) {
> > - ext2_set_link(old_inode, dir_de, dir_page, new_dir);
> > + /* Set link only if parent has changed and thus avoid setting
> > + * of mtime of the moved directory on a pure rename. */
> > + if (old_dir != new_dir)
> > + ext2_set_link(old_inode, dir_de, dir_page, new_dir);
> > inode_dec_link_count(old_dir);
> > }
> > return 0;
>
> hm, what do other filesystems do? We risk breaking things in either case.
> Probably changing ext2 is safer than changing ext3/4, given that ext2 is
> used less.
Yes, I think so as well. Looking more into what other filesystems do, it
seems that FAT, UDF, reiserfs, ext3, ext4 actually never update mtime of
the moved directory, even if the parent has changed. So maybe it would make
more sence to change ext2 in this way as well. What do you think?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2009-04-09 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 18:41 [PATCH] ext2: Do not update mtime of a move directory when parent has not changed Jan Kara
2009-04-09 18:51 ` Andrew Morton
2009-04-09 19:15 ` Jan Kara [this message]
2009-04-09 20:20 ` Andrew Morton
2009-04-10 14:13 ` Jan Kara
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=20090409191515.GB3886@duck.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hare@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=ronny.pretzsch@dfs.de \
/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