linux-kernel - Re: [PATCH v4] relatime: Make relatime smarter

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]

Date:	Fri, 28 Nov 2008 13:41:19 +0000
From:	Matthew Garrett <mjg@...hat.com>
To:	Andreas Dilger <adilger@....com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	mingo@...hat.com, val.henson@...il.com, matthew@....cx
Subject: Re: [PATCH v4] relatime: Make relatime smarter

On Thu, Nov 27, 2008 at 03:08:39PM -0700, Andreas Dilger wrote:

> The one problem with a 1-day default is that cron jobs like updatedb will
> revert to updating the atime on every single file every day.  It would be
> better to make it slightly more than 1 day (e.g. 25h) to avoid this and
> at least defer atime updates to every other day for files that are not
> otherwise accessed except by cron.

I don't see the real benefit to this. If you want to prevent atime 
updates entirely, use noatime rather than relatime. Increasing the 
timeout just means that you get increased disk activity every other day 
rather than every day, which isn't really the problem we're trying to 
solve.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/