linux-kernel - Re: relatime: update once per day patches (was: ext3 IO latency measurements)

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: <alpine.LFD.2.00.0903260912270.3032@localhost.localdomain>
Date:	Thu, 26 Mar 2009 09:14:28 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Frans Pop <elendil@...net.nl>, mingo@...e.hu, tytso@....edu,
	jack@...e.cz, alan@...rguk.ukuu.org.uk, arjan@...radead.org,
	a.p.zijlstra@...llo.nl, npiggin@...e.de, jens.axboe@...cle.com,
	drees76@...il.com, jesper@...gh.cc, linux-kernel@...r.kernel.org,
	oleg@...hat.com, roland@...hat.com
Subject: Re: relatime: update once per day patches (was: ext3 IO latency
 measurements)



On Thu, 26 Mar 2009, Andrew Morton wrote:
> 
> Hard-wiring a 24-hour interval into the core VFS for all mounted
> filesystems is dumb.

Umm. 

I generally agree witht he "leave policy to user space" people, but this 
is an area where (a) user space has shown itself to not get it right (ie 
people don't do even the existing relatime because distros don't) and (b) 
what's the alternative?

> I (and others) pointed out that it would be better to implement this as
> a mount option.  That suggestion was met with varying sillinesses and
> that is where things stand.

I'd suggest first just doing the 24 hour thing, and then, IF user space 
actually ever gets its act together, and people care, and they _ask_ for a 
mount option, that's when it's worth doing.

			Linus
--
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/