From: Chuck Lever <cel@kernel.org>
To: viro@zeniv.linux.org.uk, brauner@kernel.org, hughd@google.com,
akpm@linux-foundation.org
Cc: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
jlayton@redhat.com, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v4 0/3] shmemfs stable directory offsets
Date: Mon, 26 Jun 2023 14:21:20 -0400 [thread overview]
Message-ID: <168780354647.2142.537463116658872680.stgit@manet.1015granger.net> (raw)
The following series is for continued discussion of the need for
and implementation of stable directory offsets for shmemfs/tmpfs.
Changes since v3:
- Rebased on v6.4
- Fixed error handling bugs
Changes since v2:
- Move bulk of stable offset support into fs/libfs.c
- Replace xa_find_after with xas_find_next for efficiency
Changes since v1:
- Break the single patch up into a series
Changes since RFC:
- Destroy xarray in shmem_destroy_inode() instead of free_in_core_inode()
- A few cosmetic updates
---
Chuck Lever (3):
libfs: Add directory operations for stable offsets
shmem: Refactor shmem_symlink()
shmem: stable directory offsets
fs/dcache.c | 1 +
fs/libfs.c | 185 +++++++++++++++++++++++++++++++++++++++++
include/linux/dcache.h | 1 +
include/linux/fs.h | 9 ++
mm/shmem.c | 69 +++++++++++----
5 files changed, 250 insertions(+), 15 deletions(-)
--
Chuck Lever
next reply other threads:[~2023-06-26 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 18:21 Chuck Lever [this message]
2023-06-26 18:21 ` [PATCH v4 1/3] libfs: Add directory operations for stable offsets Chuck Lever
2023-06-27 6:44 ` Christoph Hellwig
2023-06-27 8:52 ` Christian Brauner
2023-06-27 14:04 ` Chuck Lever III
2023-06-27 14:19 ` Jeff Layton
2023-06-26 18:21 ` [PATCH v4 2/3] shmem: Refactor shmem_symlink() Chuck Lever
2023-06-27 6:44 ` Christoph Hellwig
2023-06-26 18:21 ` [PATCH v4 3/3] shmem: stable directory offsets Chuck Lever
2023-06-27 14:06 ` Bernd Schubert
2023-06-27 14:11 ` Chuck Lever III
2023-06-27 14:48 ` Bernd Schubert
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=168780354647.2142.537463116658872680.stgit@manet.1015granger.net \
--to=cel@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hughd@google.com \
--cc=jlayton@kernel.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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