From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "idryomov@gmail.com" <idryomov@gmail.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: RE: [PATCH 3/3] ceph: fix a race with rename() in ceph_mdsc_build_path()
Date: Tue, 17 Jun 2025 22:12:08 +0000 [thread overview]
Message-ID: <cd929637ed2826f25d15bad39a884fac3fd30d0c.camel@ibm.com> (raw)
In-Reply-To: <20250617220122.GM1880847@ZenIV>
On Tue, 2025-06-17 at 23:01 +0100, Al Viro wrote:
> 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...
Frankly speaking, your tree could be the faster way to upstream. However, I can
push this patch set into the ceph tree for more deeper testing in the internal
testing infrastructure. But I don't expect any serious issues in the patches
that could introduce some bugs.
Ilya,
What is your opinion on this? Would you prefer to go through the ceph tree?
Thanks,
Slava.
next prev parent reply other threads:[~2025-06-17 22:12 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
2025-06-17 22:12 ` Viacheslav Dubeyko [this message]
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=cd929637ed2826f25d15bad39a884fac3fd30d0c.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).