public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Yu Kuai <yukuai1@huaweicloud.com>,
	sashal@kernel.org, stable@vger.kernel.org, song@kernel.org,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com,
	johnny.chenyi@huawei.com
Subject: Re: [PATCH 6.1 0/2] md: fix mddev uaf while iterating all_mddevs list
Date: Thu, 24 Apr 2025 12:26:42 +0200	[thread overview]
Message-ID: <2025042436-iodize-dazzler-e7b2@gregkh> (raw)
In-Reply-To: <aAoFRJ_RIq6pdyn9@eldamar.lan>

On Thu, Apr 24, 2025 at 11:32:52AM +0200, Salvatore Bonaccorso wrote:
> Hi Greg,
> 
> On Thu, Apr 24, 2025 at 08:40:41AM +0200, Greg KH wrote:
> > On Wed, Apr 23, 2025 at 08:14:09PM +0200, Salvatore Bonaccorso wrote:
> > > Hi Greg, Sasha, Yu,
> > > 
> > > On Sat, Apr 19, 2025 at 09:23:01AM +0800, Yu Kuai wrote:
> > > > From: Yu Kuai <yukuai3@huawei.com>
> > > > 
> > > > Hi, Greg
> > > > 
> > > > This is the manual adaptation version for 6.1, for 6.6/6.12 commit
> > > > 8542870237c3 ("md: fix mddev uaf while iterating all_mddevs list") can
> > > > be applied cleanly, can you queue them as well?
> > > > 
> > > > Thanks!
> > > > 
> > > > Yu Kuai (2):
> > > >   md: factor out a helper from mddev_put()
> > > >   md: fix mddev uaf while iterating all_mddevs list
> > > > 
> > > >  drivers/md/md.c | 50 +++++++++++++++++++++++++++++--------------------
> > > >  1 file changed, 30 insertions(+), 20 deletions(-)
> > > 
> > > I noticed that the change 8542870237c3 was queued for 6.6.y and 6.12.y
> > > and is in the review now, but wonder should we do something more with
> > > 6.1.y as this requires this series/manual adaption?
> > > 
> > > Or will it make for the next round of stable updates in 6.1.y? 
> > > 
> > > (or did it just felt through the cracks and it is actually fine that I
> > > ping the thread on this question).
> > 
> > This fell through the cracks and yes, it is great that you pinged it.
> > I'll queue it up for the next release, thanks!
> 
> Thank you! Very much appreciated! (People installing Debian will be
> happy as it affects kernel under certiain circumstances, cf.
> https://bugs.debian.org/1086175, https://bugs.debian.org/1089158, but
> was longstanding already).

Now queued up, thanks.

greg k-h

      reply	other threads:[~2025-04-24 10:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19  1:23 [PATCH 6.1 0/2] md: fix mddev uaf while iterating all_mddevs list Yu Kuai
2025-04-19  1:23 ` [PATCH 6.1 1/2] md: factor out a helper from mddev_put() Yu Kuai
2025-04-19 12:19   ` Sasha Levin
2025-04-19  1:23 ` [PATCH 6.1 2/2] md: fix mddev uaf while iterating all_mddevs list Yu Kuai
2025-04-19 12:19   ` Sasha Levin
2025-04-23 18:14 ` [PATCH 6.1 0/2] " Salvatore Bonaccorso
2025-04-24  6:40   ` Greg KH
2025-04-24  9:32     ` Salvatore Bonaccorso
2025-04-24 10:26       ` Greg KH [this message]

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=2025042436-iodize-dazzler-e7b2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=carnil@debian.org \
    --cc=johnny.chenyi@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=song@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.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