public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Yu Kuai <yukuai1@huaweicloud.com>,
	gregkh@linuxfoundation.org, sashal@kernel.org
Cc: 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: Wed, 23 Apr 2025 20:14:09 +0200	[thread overview]
Message-ID: <aAkt8WLN1Gb9snv-@eldamar.lan> (raw)
In-Reply-To: <20250419012303.85554-1-yukuai1@huaweicloud.com>

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).

Regards,
Salvatore

  parent reply	other threads:[~2025-04-23 18:14 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 ` Salvatore Bonaccorso [this message]
2025-04-24  6:40   ` [PATCH 6.1 0/2] " Greg KH
2025-04-24  9:32     ` Salvatore Bonaccorso
2025-04-24 10:26       ` Greg KH

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=aAkt8WLN1Gb9snv-@eldamar.lan \
    --to=carnil@debian.org \
    --cc=gregkh@linuxfoundation.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