From: Al Viro <viro@zeniv.linux.org.uk>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ceph: fix a race with rename() in ceph_mdsc_build_path()
Date: Tue, 17 Jun 2025 23:01:22 +0100 [thread overview]
Message-ID: <20250617220122.GM1880847@ZenIV> (raw)
In-Reply-To: <f9008d5161cb8a7cdfed54da742939523641532d.camel@ibm.com>
On Tue, Jun 17, 2025 at 06:21:38PM +0000, Viacheslav Dubeyko wrote:
> Tested-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
> Reviewed-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
OK, tested-by/reviewed-by applied to commits in that branch, branch
force-pushed to the same place
(git.kernel.org:/pub/scm/linux/kernel/git/viro/vfs.git work.ceph-d_name-fixes)
Would you prefer to merge it via the ceph tree? Or I could throw it
into my #for-next and push it to Linus come the next window - up to you...
next prev parent reply other threads:[~2025-06-17 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 6:20 [PATCHES] ceph d_name race fixes Al Viro
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 [this message]
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=20250617220122.GM1880847@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;
as well as URLs for NNTP newsgroup(s).