From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Cc: mj@mjturner.net
Subject: Re: [PATCH] don't update mtime on rename source
Date: Tue, 24 Jun 2008 10:17:19 +0200 [thread overview]
Message-ID: <20080624081719.GA31440@lst.de> (raw)
In-Reply-To: <20080624081348.GA31048@lst.de>
Sorry for the missing subject, should be the one in this mail
On Tue, Jun 24, 2008 at 10:13:48AM +0200, Christoph Hellwig wrote:
> As reported by Michael-John Turner XFS updates the mtime on the source
> inode of a rename call in case it's a directory and changes the parent.
>
> This doesn't make any sense, is not mentioned in the standards and not
> performed by any other Linux filesystems so remove it.
>
>
> (resending this as it might have been lost in the previous thread)
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Index: linux-2.6-xfs/fs/xfs/xfs_rename.c
> ===================================================================
> --- linux-2.6-xfs.orig/fs/xfs/xfs_rename.c 2008-06-18 18:24:38.000000000 +0200
> +++ linux-2.6-xfs/fs/xfs/xfs_rename.c 2008-06-18 18:30:17.000000000 +0200
> @@ -336,22 +336,18 @@ xfs_rename(
> ASSERT(error != EEXIST);
> if (error)
> goto abort_return;
> - xfs_ichgtime(src_ip, XFS_ICHGTIME_MOD | XFS_ICHGTIME_CHG);
> -
> - } else {
> - /*
> - * We always want to hit the ctime on the source inode.
> - * We do it in the if clause above for the 'new_parent &&
> - * src_is_directory' case, and here we get all the other
> - * cases. This isn't strictly required by the standards
> - * since the source inode isn't really being changed,
> - * but old unix file systems did it and some incremental
> - * backup programs won't work without it.
> - */
> - xfs_ichgtime(src_ip, XFS_ICHGTIME_CHG);
> }
>
> /*
> + * We always want to hit the ctime on the source inode.
> + *
> + * This isn't strictly required by the standards since the source
> + * inode isn't really being changed, but old unix file systems did
> + * it and some incremental backup programs won't work without it.
> + */
> + xfs_ichgtime(src_ip, XFS_ICHGTIME_CHG);
> +
> + /*
> * Adjust the link count on src_dp. This is necessary when
> * renaming a directory, either within one parent when
> * the target existed, or across two parent directories.
---end quoted text---
prev parent reply other threads:[~2008-06-24 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 8:13 [PATCH] Christoph Hellwig
2008-06-24 8:17 ` Christoph Hellwig [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=20080624081719.GA31440@lst.de \
--to=hch@lst.de \
--cc=mj@mjturner.net \
--cc=xfs@oss.sgi.com \
/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