linux-kernel - Re: ext4 bug? last write time precedes last mount time on a writable volume!

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120302204521.GD22215@thunk.org>
Date:	Fri, 2 Mar 2012 15:45:21 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Neil Clarkson <neilaclarkson@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ext4 bug? last write time precedes last mount time on a
 writable volume!

On Fri, Mar 02, 2012 at 12:39:57PM +0000, Neil Clarkson wrote:
> Isn't the s_wtime field of the ext4 superblock supposed to show the
> time, in seconds since the epoch, of the last write? It isn't
> happening!

It shows the last time the superblock has been modified, and one of
the things that we've been doing lately has been to optimize ext4 so
that it writes to the superblock *much* less often.  It was a
performance bottleneck to be constantly updating the number of free
blocks in the superblock each time we write to a new block, for
example --- or update the superblock to update the number of free
inodes each time we allocate a new inode.

Is there a reason why you particularly care about s_wtime being
updated?

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/