public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>, ceph-devel@vger.kernel.org
Subject: [PATCHES] ceph d_name race fixes
Date: Sat, 14 Jun 2025 07:20:51 +0100	[thread overview]
Message-ID: <20250614062051.GC1880847@ZenIV> (raw)

	Series of race fixes for d_name handling in ceph had been posted
back in February, but apparently had fallen through the cracks - I expected
ceph folks to pull (or cherry-pick) it, they apparently thought I'd send
it to Linus and nobody checked what actually went down...

	I've rebased it to 6.16-rc1, with a couple of cosmetical changes
suggested back then.  Currently it's in
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.ceph-d_name-fixes
Individual patches in followups.

	Folks, could you test and review it?  I really don't care which
tree would it go through, just let's make sure that everyone agrees who
pushes it out...

Shortlog:
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()

Diffstat:
 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(-)

             reply	other threads:[~2025-06-14  6:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14  6:20 Al Viro [this message]
2025-06-14  6:22 ` [PATCH 1/3] [ceph] parse_longname(): strrchr() expects NUL-terminated string Al Viro
2025-06-14  6:22   ` [PATCH 2/3] prep for ceph_encode_encrypted_fname() fixes Al Viro
2025-06-17 18:20     ` Viacheslav Dubeyko
2025-06-14  6:22   ` [PATCH 3/3] ceph: fix a race with rename() in ceph_mdsc_build_path() Al Viro
2025-06-17 18:21     ` Viacheslav Dubeyko
2025-06-17 22:01       ` Al Viro
2025-06-17 22:12         ` Viacheslav Dubeyko
2025-06-17 22:15           ` Al Viro
2025-06-19 18:04             ` Viacheslav Dubeyko
2025-06-19 19:53               ` Al Viro
2025-06-16 17:42   ` [PATCH 1/3] [ceph] parse_longname(): strrchr() expects NUL-terminated string Viacheslav Dubeyko
2025-06-17 18:20   ` Viacheslav Dubeyko

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=20250614062051.GC1880847@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=Slava.Dubeyko@ibm.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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