linux-kernel - Re: [RFC] [PATCH] Relative lazy atime

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: <20060805183609.GA7564@tuatara.stupidest.org>
Date:	Sat, 5 Aug 2006 11:36:09 -0700
From:	Chris Wedgwood <cw@...f.org>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Dave Kleikamp <shaggy@...tin.ibm.com>,
	Christoph Hellwig <hch@....de>,
	Valerie Henson <val_henson@...ux.intel.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Akkana Peck <akkana@...llowsky.com>,
	Mark Fasheh <mark.fasheh@...cle.com>,
	Jesse Barnes <jesse.barnes@...el.com>, jsipek@...sunysb.edu,
	Al Viro <viro@....linux.org.uk>
Subject: Re: [RFC] [PATCH] Relative lazy atime

On Sat, Aug 05, 2006 at 07:04:34PM +0200, Arjan van de Ven wrote:

> the vfs shouldn't consider it clean, it should consider it
> "atime-only dirty".. with that many of the vfs interaction issues
> ought to go away

should it be atime-dirty or non-critical-dirty? (ie. make it more
generic to cover cases where we might have other non-critical fields
to flush if we can but can tolerate loss if we dont)

adminitedly atime is the only one i can think of now
-
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/