| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Directory mtime update issue (kernel 2.6.25) |
| From: | Michael-John Turner <mj@xxxxxxxxxxxx> |
| Date: | Wed, 18 Jun 2008 23:30:50 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20080618163356.GA6330@infradead.org> |
| References: | <20080618144534.GC11301@aurora.pimp.org.za> <20080618163356.GA6330@infradead.org> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (NetBSD aurora.pimp.org.za 4.0_STABLE sparc64) |
On Wed, Jun 18, 2008 at 12:33:56PM -0400, Christoph Hellwig wrote: > Below is an untested patch to always just update the ctime: Just a quick update - the patch does the trick and changes the rename(2) behaviour to be what I expect. Now, when a directory is renamed, its mtime doesn't change, even if it has a new parent. -mj -- Michael-John Turner mj@xxxxxxxxxxxx <> http://mjturner.net/ |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Directory mtime update issue (kernel 2.6.25), Michael-John Turner |
|---|---|
| Next by Date: | Re: XFS: 2.6.26-rc6 link count mismatch for inode, Dave Chinner |
| Previous by Thread: | Re: Directory mtime update issue (kernel 2.6.25), Christoph Hellwig |
| Next by Thread: | is the flush-on-close-after-truncate still needed?, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |