From: Luis Chamberlain <mcgrof@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: "Latchesar Ionkov" <lucho@ionkov.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
"Anders Larsen" <al@alarsen.net>,
"Carlos Llamas" <cmllamas@google.com>,
"Hugh Dickins" <hughd@google.com>,
"John Johansen" <john.johansen@canonical.com>,
"Seth Forshee" <sforshee@digitalocean.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christoph Hellwig" <hch@lst.de>,
"Mike Marshall" <hubcap@omnibond.com>,
"Paulo Alcantara" <pc@manguebit.com>,
linux-xfs@vger.kernel.org, "Bart Van Assche" <bvanassche@acm.org>,
"John Keeping" <john@keeping.me.uk>,
"Zhang Yi" <yi.zhang@huawei.com>,
"James Morris" <jmorris@namei.org>,
"Tyler Hicks" <code@tyhicks.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
devel@lists.orangefs.org,
"Shyam Prasad N" <sprasad@microsoft.com>,
"Jan Harkes" <jaharkes@cs.cmu.edu>,
linux-um@lists.infradead.org,
"Nicholas Piggin" <npiggin@gmail.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Eric Van Hensbergen" <ericvh@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Trond Myklebust" <trond.myklebust@hammerspace.com>,
"Anton Altaparmakov" <anton@tuxera.com>,
"Christian Brauner" <brauner@kernel.org>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Stephen Smalley" <stephen.smalley.work@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ronnie Sahlberg" <lsahlber@redhat.com>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Jan Kara" <jack@suse.com>,
"Tejun Heo" <tj@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-trace-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
"Dave Kleikamp" <shaggy@kernel.org>,
"Sandeep Dhavale" <dhavale@google.com>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
"Mimi Zohar" <zohar@linux.ibm.com>,
linux-mm@kvack.org, "Joel Fernandes" <joel@joelfernande>
Subject: Re: [PATCH 01/79] fs: add ctime accessors infrastructure
Date: Fri, 30 Jun 2023 15:12:43 -0700 [thread overview]
Message-ID: <ZJ9TW9MQmlqmbRU/@bombadil.infradead.org> (raw)
In-Reply-To: <20230621144507.55591-2-jlayton@kernel.org>
On Wed, Jun 21, 2023 at 10:45:06AM -0400, Jeff Layton wrote:
> struct timespec64 has unused bits in the tv_nsec field that can be used
> for other purposes. In future patches, we're going to change how the
> inode->i_ctime is accessed in certain inodes in order to make use of
> them. In order to do that safely though, we'll need to eradicate raw
> accesses of the inode->i_ctime field from the kernel.
>
> Add new accessor functions for the ctime that we can use to replace them.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Luis
next prev parent reply other threads:[~2023-07-01 3:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 14:45 [PATCH 00/79] fs: new accessors for inode->i_ctime Jeff Layton
2023-06-21 14:45 ` [PATCH 01/79] fs: add ctime accessors infrastructure Jeff Layton
2023-06-21 16:34 ` Jan Kara
2023-06-21 17:29 ` Tom Talpey
2023-06-21 18:01 ` Jeff Layton
2023-06-21 18:19 ` Tom Talpey
2023-06-21 18:48 ` Jeff Layton
2023-06-22 0:46 ` Damien Le Moal
2023-06-22 10:14 ` Jeff Layton
2023-06-30 22:12 ` Luis Chamberlain [this message]
2023-07-12 15:31 ` Randy Dunlap
2023-06-21 14:45 ` [PATCH 02/79] spufs: switch to new ctime accessors Jeff Layton
2023-06-21 16:34 ` Jan Kara
2023-06-22 0:19 ` Jeremy Kerr
2023-06-21 14:49 ` [PATCH 79/79] fs: rename i_ctime field to __i_ctime Jeff Layton
2023-06-21 19:21 ` [PATCH 00/79] fs: new accessors for inode->i_ctime Steven Rostedt
2023-06-21 19:52 ` Jeff Layton
2023-06-23 12:41 ` Christian Brauner
2023-06-30 22:11 ` Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZJ9TW9MQmlqmbRU/@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=al@alarsen.net \
--cc=anton@tuxera.com \
--cc=arve@android.com \
--cc=borntraeger@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=cmllamas@google.com \
--cc=code@tyhicks.com \
--cc=devel@lists.orangefs.org \
--cc=dhavale@google.com \
--cc=djwong@kernel.org \
--cc=ericvh@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=hughd@google.com \
--cc=jack@suse.com \
--cc=jaharkes@cs.cmu.edu \
--cc=jlayton@kernel.org \
--cc=jmorris@namei.org \
--cc=joel@joelfernande \
--cc=john.johansen@canonical.com \
--cc=john@keeping.me.uk \
--cc=jolsa@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=lucho@ionkov.net \
--cc=npiggin@gmail.com \
--cc=pc@manguebit.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rafael@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=sforshee@digitalocean.com \
--cc=shaggy@kernel.org \
--cc=sprasad@microsoft.com \
--cc=stephen.smalley.work@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=surenb@google.com \
--cc=svens@linux.ibm.com \
--cc=tj@kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wsa+renesas@sang-engineering.com \
--cc=yi.zhang@huawei.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).