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: <200903270115.32071.elendil@planet.nl>
Date:	Fri, 27 Mar 2009 01:15:27 +0100
From:	Frans Pop <elendil@...net.nl>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	alan@...rguk.ukuu.org.uk, mjg@...hat.com, tytso@....edu,
	mingo@...e.hu, jack@...e.cz, akpm@...ux-foundation.org,
	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: [PATCH 2/2] Make relatime default

Linus Torvalds wrote:
> If the distro's had done this right in the year+ that this has been in,
> I might consider your NAK to have some weight.
> 
> As it is, we know that didn't happen, and we've had three different
> people from different distributions say that they wanted to use relatime
> anyway, so it's now the default in my git tree.
> 
> If you want to live in some dark ages, you can do so with the
> "strictatime" thing.

I obviously welcome the inclusion of the first patch and I'm neutral about 
the second one, but I'm not at all sure that making relatime the default 
(yet) is the right thing, especially as util-linux' mount command does 
not yet even support that "strictatime" thing. Shouldn't that at least 
happen first (and have been supported in distro's stable releases for 
some time)?

I guess users and distros can still elect not to set it as default, but it 
still seems a bit like going from one extreme to another.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ