[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025042418-come-vacant-ec55@gregkh>
Date: Thu, 24 Apr 2025 08:40:41 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Salvatore Bonaccorso <carnil@...ian.org>
Cc: Yu Kuai <yukuai1@...weicloud.com>, sashal@...nel.org,
stable@...r.kernel.org, song@...nel.org, linux-raid@...r.kernel.org,
linux-kernel@...r.kernel.org, yukuai3@...wei.com,
yi.zhang@...wei.com, yangerkun@...wei.com, johnny.chenyi@...wei.com
Subject: Re: [PATCH 6.1 0/2] md: fix mddev uaf while iterating all_mddevs list
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@...wei.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!
greg k-h
Powered by blists - more mailing lists