linux-ext4 - Re: [Bugme-new] [Bug 10276] New: directory ctime not updated by rename

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080318105403.8b2d8d8c.akpm@linux-foundation.org>
Date:	Tue, 18 Mar 2008 10:54:03 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
	Christoph Hellwig <hch@....de>,
	bugme-daemon@...zilla.kernel.org,
	lasse-kernelbug-2008@...l.plastictree.net
Subject: Re: [Bugme-new] [Bug 10276] New: directory ctime not updated by
 rename

On Tue, 18 Mar 2008 17:46:09 +0000 Al Viro <viro@...IV.linux.org.uk> wrote:

> On Tue, Mar 18, 2008 at 10:00:23AM -0700, Andrew Morton wrote:
> 
> > Do we agree that this is a bug?  If so, is it a VFS thing or a per-fs
> > thing?
> 
> The latter; all control over timestamps on directory operations is in
> filesystems.

OK

>  Which filesystem it is, BTW?

ext3.

>  E.g. ext2 has
>         dir->i_mtime = dir->i_ctime = CURRENT_TIME_SEC;
> in ext2_set_link() (and the same in ext2_add_entry()/ext2_delete_entry()),
> so on all paths in ext2_rename() both parents will get ctime and mtime
> updated; so will the object being moved and the object being unlinked
> (explicitly in ext2_rename()).
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html