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  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]
Date:   Tue, 23 Aug 2022 21:38:07 +1000
From:   "NeilBrown" <>
To:     "Jeff Layton" <>
Cc:     "Dave Chinner" <>,
        "Mimi Zohar" <>,,,,,,,
        "Trond Myklebust" <>
Subject: Re: [PATCH] iversion: update comments with info about atime updates

On Tue, 23 Aug 2022, Jeff Layton wrote:
> So, we can refer to that and simply say:
> "If the function updates the mtime or ctime on the inode, then the
> i_version should be incremented. If only the atime is being updated,
> then the i_version should not be incremented. The exception to this rule
> is explicit atime updates via utimes() or similar mechanism, which
> should result in the i_version being incremented."

Is that exception needed?  utimes() updates ctime.

doesn't say that, but

does, as does the code.


Powered by blists - more mailing lists