mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "chenyuxi (D)" <chenyuxi19@huawei.com>
To: <max.kellermann@ionos.com>
Cc: <amarkuze@redhat.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 17:15:37 +0800	[thread overview]
Message-ID: <b8c135bf-927e-454e-8bca-cbdbae133d51@huawei.com> (raw)
In-Reply-To: <20260904150304.49104-1-max.kellermann@ionos.com>

Hi Max,

Do you have any plans to move this series forward?

Patch 1/3 completes the fix for CVE-2026-89654 (use-after-free
in check_new_map()): the earlier fix ee611a750955 still leaves
the UAF in place.  We are tracking this CVE in our
downstream kernels, so we'd really like to see the series land
in mainline.  The thread, however, has been quiet since
Sep 8th, when 3/3 picked up Xiubo's Reviewed-by, and the
patches are in neither the ceph-client testing branch nor
mainline yet.

Is there anything still holding the series back that we could
help with?

Thanks,
Chen Yuxi

  parent reply	other threads:[~2026-10-14  9:15 UTC|newest]

Thread overview: 15+ 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 ` chenyuxi (D) [this message]
2026-10-14  9:50   ` [PATCH v4 0/3] " Max Kellermann
2026-10-14 10:46     ` Alex Markuze
2026-10-14 11:27       ` Alex Markuze
2026-10-14 11:50         ` Max Kellermann
2026-10-14 17:41           ` Alex Markuze

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=b8c135bf-927e-454e-8bca-cbdbae133d51@huawei.com \
    --to=chenyuxi19@huawei.com \
    --cc=amarkuze@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --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®