[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20230713-beispiel-bezeichnen-cf537927cefd@brauner>
Date: Thu, 13 Jul 2023 16:25:50 +0200
From: Christian Brauner <brauner@...nel.org>
To: Andreas Gruenbacher <agruenba@...hat.com>,
Jeff Layton <jlayton@...nel.org>
Cc: Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org, cluster-devel@...hat.com,
linux-kernel@...r.kernel.org, Bob Peterson <rpeterso@...hat.com>
Subject: Re: [PATCH] gfs2: fix timestamp handling on quota inodes
On Thu, 13 Jul 2023 09:52:48 -0400, Jeff Layton wrote:
> While these aren't generally visible from userland, it's best to be
> consistent with timestamp handling. When adjusting the quota, update the
> mtime and ctime like we would with a write operation on any other inode,
> and avoid updating the atime which should only be done for reads.
>
>
Applied to the vfs.ctime branch of the vfs/vfs.git tree.
Patches in the vfs.ctime branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.ctime
[1/1] gfs2: fix timestamp handling on quota inodes
https://git.kernel.org/vfs/vfs/c/ea462c3f7f48
Powered by blists - more mailing lists