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
| ||
|
Message-ID: <135fb33cc23ba1ff07045637916e44f6d6614851.camel@kernel.org> Date: Thu, 19 Sep 2024 18:53:08 +0200 From: Jeff Layton <jlayton@...nel.org> To: Bagas Sanjaya <bagasdotme@...il.com>, John Stultz <jstultz@...gle.com>, Thomas Gleixner <tglx@...utronix.de>, Stephen Boyd <sboyd@...nel.org>, Alexander Viro <viro@...iv.linux.org.uk>, Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>, Steven Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Jonathan Corbet <corbet@....net>, Chandan Babu R <chandan.babu@...cle.com>, "Darrick J. Wong" <djwong@...nel.org>, Theodore Ts'o <tytso@....edu>, Andreas Dilger <adilger.kernel@...ger.ca>, Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>, David Sterba <dsterba@...e.com>, Hugh Dickins <hughd@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, Chuck Lever <chuck.lever@...cle.com>, Vadim Fedorenko <vadim.fedorenko@...ux.dev> Cc: Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, linux-doc@...r.kernel.org, linux-xfs@...r.kernel.org, linux-ext4@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-nfs@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH v8 07/11] Documentation: add a new file documenting multigrain timestamps On Mon, 2024-09-16 at 08:01 +0700, Bagas Sanjaya wrote: > On Sat, Sep 14, 2024 at 01:07:20PM -0400, Jeff Layton wrote: > > +Multigrain timestamps aim to remedy this by selectively using fine-grained > > +timestamps when a file has had its timestamps queried recently, and the current > > +coarse-grained time does not cause a change. > > Do you mean using fine-grained timestamps when timestamps of a file has been > recently queried/modified BUT its coarse-grained timestamps aren't changed? > > Confused... > Yes, I'll do an s/and/but/ there in the Documentation. Basically, we want to avoid updating the floor whenever we can (since it's a global variable), so we only get a fine-grained time if there is no other way to effect a change to the timestamps. Thanks! -- Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists