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  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]
Date:	Mon, 04 Dec 2006 10:54:53 +0000
From:	Steven Whitehouse <>
To:	Valerie Henson <>,
	Mark Fasheh <>
Subject: Re: What's in ocfs2.git


On Sun, 2006-12-03 at 12:31 -0800, Mark Fasheh wrote:
> This e-mail describes the OCFS2 patches which I intend to push
> upstream to Linus for 2.6.20.
> * Atime updates - thanks to Tiger Yang <>, ocfs2 now
>   writes to the inode atime field. This doesn't require any disk changes,
>   and is completely backwards compatible with older ocfs2 versions. An
>   inodes Atime is only updated if it hasn't changed within a certain
>   quantum. The user can define their own value at mount time, with 0
>   indicating that atime should always be updated. This is very similar to
>   the scheme implemented by gfs2. In the future, I'd like to see a "relative
>   atime" mode, which functions in the manner described by Valerie Henson at:
I'd like to second that. [adding Val Henson to the "to"] What (if
anything) remains to be done before the relative atime patch is ready to
go upstream? I'm happy to help out here if required,


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists