From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
ceph-devel@vger.kernel.org
Subject: [git pull][6.17] vfs.git 7/9: ceph d_name fixes
Date: Sat, 26 Jul 2025 09:08:05 +0100 [thread overview]
Message-ID: <20250726080805.GF1456602@ZenIV> (raw)
In-Reply-To: <20250726080119.GA222315@ZenIV>
stuff that had fallen through the cracks back in February; ceph folks tested
that pile and said they prefer to have it go through my tree...
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-ceph-d_name-fixes
for you to fetch changes up to 0d2da2561bdeb459b6c540c2417a15c1f8732e6a:
ceph: fix a race with rename() in ceph_mdsc_build_path() (2025-06-17 17:58:14 -0400)
----------------------------------------------------------------
ceph ->d_name race fixes
----------------------------------------------------------------
Al Viro (3):
[ceph] parse_longname(): strrchr() expects NUL-terminated string
prep for ceph_encode_encrypted_fname() fixes
ceph: fix a race with rename() in ceph_mdsc_build_path()
fs/ceph/caps.c | 18 +++++-------
fs/ceph/crypto.c | 82 +++++++++++++++++-----------------------------------
fs/ceph/crypto.h | 18 +++---------
fs/ceph/dir.c | 7 ++---
fs/ceph/mds_client.c | 4 +--
5 files changed, 43 insertions(+), 86 deletions(-)
next prev parent reply other threads:[~2025-07-26 8:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 8:01 [git pull][6.17] vfs.git 1/9: d_flags pile Al Viro
2025-07-26 8:02 ` [git pull][6.17] vfs.git 2/9: simple_recursive_removal Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:03 ` [git pull][6.17] vfs.git 3/9: rpc_pipefs Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:04 ` [git pull][6.17] vfs.git 4/9: asm/param.h pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:05 ` [git pull][6.17] vfs.git 5/9: securityfs Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:05 ` [git pull][6.17] vfs.git 6/9: misc pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:08 ` Al Viro [this message]
2025-07-28 23:41 ` [git pull][6.17] vfs.git 7/9: ceph d_name fixes pr-tracker-bot
2025-07-26 8:08 ` [git pull][6.17] vfs.git 8/9: CLASS(fd) followup Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:09 ` [git pull][6.17] vfs.git 9/9: mount pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-28 23:41 ` [git pull][6.17] vfs.git 1/9: d_flags pile pr-tracker-bot
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=20250726080805.GF1456602@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=Slava.Dubeyko@ibm.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).