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] [day] [month] [year] [list]
Message-ID: <20090108133220.GA11254@srcf.ucam.org>
Date:	Thu, 8 Jan 2009 13:32:20 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Peter Moulder <pjrm@...l.internode.on.net>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Éric Piel <E.A.B.Piel@...elft.nl>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH, resend] relatime: Let relatime update atime at least once per day

On Thu, Jan 08, 2009 at 11:29:53PM +1100, Peter Moulder wrote:
> What was the fate of Ingo's previous patch[*1] to implement this (which,
> incidentally, also included updates to documentation and made the interval
> configurable as Éric Piel suggests) ?

Nobody merged it and Ingo got bored of pushing it. I sent it earlier, 
but nobody came up with an especially good argument for the 
configurability and everyone seemed to want to paint the patch pink with 
yellow polka dots, so I gave up and just sent a minimal one in the hope 
that nobody could find anything to complain about.

> Just a minor nit, but the patch description (not included in the patch itself)
> "at least once a day" isn't particularly accurate given that the patch enforces
> at least a day [minus a second or so] has elapsed since the last update.  The
> description in the above-referenced patch "only once a day" better captures the
> situation, I think.

If mtime is changed then atime will be updated on the next access, so 
you can easily have more than one atime update a day.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ