From: Alex Markuze <amarkuze@redhat.com>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: "chenyuxi (D)" <chenyuxi19@huawei.com>,
ceph-devel@vger.kernel.org, idryomov@gmail.com,
linux-kernel@vger.kernel.org, xiubo.li@clyso.com
Subject: Re: [PATCH v4 0/3] ceph: don't unregister an MDS session before removing its caps
Date: Wed, 14 Oct 2026 13:46:42 +0300 [thread overview]
Message-ID: <CAO8a2Sj2UbocxY+_MRdcH1TWht=UJT+ANWmzqLY9MQxZ0ujUpw@mail.gmail.com> (raw)
In-Reply-To: <CAKPOu+_Msno=mux+FUc-oV1-ywRFujJcnKS2HNv0sjtRVtUP3A@mail.gmail.com>
Since the last merge with main Linux the testing branch has grown by
upwards of 100 acked patches.
Xiubo acked your patch, which is good enough for me, Xiubo is back on
the maintainers list for ceph client.
I'll take another look at the discussion for fairness' sake.
Feel free to submit and argue for any other patches you feel are necessary.
If a patch solves a problem or adds needed functionality it will be
reviewed and applied as always.
On Wed, Oct 14, 2026 at 12:50 PM Max Kellermann
<max.kellermann@ionos.com> wrote:
>
> On Wed, Oct 14, 2026 at 11:15 AM chenyuxi (D) <chenyuxi19@huawei.com> wrote:
> > Do you have any plans to move this series forward?
> [...]
> > Is there anything still holding the series back that we could
> > help with?
>
> It was rejected by Alex Markuze, and he never replied to me after I
> questioned the two reviews. That's what's holding this back.
>
> As for my plans - I have more Ceph unpublished fixes in our internal
> Linux kernel fork, but I'm not submitting them, see
> https://lore.kernel.org/ceph-devel/CAKPOu+8SiwxT_44e63-EZ4T_4d-tGjwmk_Lx8i4KgZOL5JnMtQ@mail.gmail.com/
> for why.
> I just looked it up: the stack of Ceph patches in our fork has grown
> to 67 patches. They were either rejected or ignored. One of the
> rejected patches fixes a security vulnerability.
>
> --
> Max Kellermann
> Principal Architect
> Hosting Technology
>
> cm4all | Im Mediapark 6a | 50670 Köln | Germany
> General information about the company can be found here:
> https://www.cm4all.com/impressum
> A member of the IONOS Group
>
next prev parent reply other threads:[~2026-10-14 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 15:03 Max Kellermann
2026-09-04 15:03 ` [PATCH v4 1/3] ceph: fix use-after-free in check_new_map() after early session put Max Kellermann
2026-09-05 1:52 ` Xiubo Li
2026-09-04 15:03 ` [PATCH v4 2/3] ceph: stop checking a stale MDS map after dropping mutex Max Kellermann
2026-09-05 1:52 ` Xiubo Li
2026-09-04 15:03 ` [PATCH v4 3/3] ceph: don't unregister an MDS session before removing its caps Max Kellermann
2026-09-05 1:56 ` Xiubo Li
2026-09-07 19:15 ` Max Kellermann
2026-09-08 1:34 ` Xiubo Li
2026-10-14 9:15 ` [PATCH v4 0/3] " chenyuxi (D)
2026-10-14 9:50 ` Max Kellermann
2026-10-14 10:46 ` Alex Markuze [this message]
2026-10-14 11:27 ` Alex Markuze
2026-10-14 11:50 ` Max Kellermann
2026-10-14 17:41 ` Alex Markuze
2026-10-15 14:07 ` Max Kellermann
2026-10-15 16:22 ` Alex Markuze
2026-10-15 17:15 ` Max Kellermann
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='CAO8a2Sj2UbocxY+_MRdcH1TWht=UJT+ANWmzqLY9MQxZ0ujUpw@mail.gmail.com' \
--to=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chenyuxi19@huawei.com \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=xiubo.li@clyso.com \
/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
all inboxes | Powered by JetHome®