From: Greg KH <gregkh@linuxfoundation.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
xni@redhat.com, Song Liu <song@kernel.org>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: Patch "md: call del_gendisk in control path" has been added to the 6.6-stable tree
Date: Mon, 18 Aug 2025 08:38:44 +0200 [thread overview]
Message-ID: <2025081804-gloater-brought-c097@gregkh> (raw)
In-Reply-To: <0c083639-eb30-2830-0938-20684db3914a@huaweicloud.com>
On Mon, Aug 18, 2025 at 02:26:23PM +0800, Yu Kuai wrote:
> Hi,
>
> 在 2025/08/18 13:55, Greg KH 写道:
> > On Mon, Aug 18, 2025 at 09:03:39AM +0800, Yu Kuai wrote:
> > > Hi,
> > >
> > > 在 2025/08/17 22:18, Sasha Levin 写道:
> > > > This is a note to let you know that I've just added the patch titled
> > > >
> > > > md: call del_gendisk in control path
> > > >
> > > > to the 6.6-stable tree which can be found at:
> > > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > > >
> > > > The filename of the patch is:
> > > > md-call-del_gendisk-in-control-path.patch
> > > > and it can be found in the queue-6.6 subdirectory.
> > > >
> > > > If you, or anyone else, feels it should not be added to the stable tree,
> > > > please let <stable@vger.kernel.org> know about it.
> > > >
> > > >
> > > This patch should be be backported to any stable kernel, this change
> > > will break user tools mdadm:
> > >
> > > https://lore.kernel.org/all/f654db67-a5a5-114b-09b8-00db303daab7@redhat.com/
> >
> > Is it reverted in Linus's tree?
> >
>
> No, we'll not revert it, this is an improvement. In order to keep user
> tools compatibility, we added a switch in the kernel. As discussed in
> the thread, for old tools + new kernel, functionality is the same,
> however, there will be kernel warning about deprecated behaviour to
> inform user upgrading user tools.
>
> However, I feel this new warning messages is not acceptable for
> stable kernels.
Why? What is so special about stable kernels that taking the same
functionality in newer kernels is not ok?
Why not just "warn" the same here if you want to fix an issue where
userspace should be also updating some tools. As long as you aren't
breaking anything, it should be fine, right?
Or are you breaking existing workflows? You should be able to take a
new kernel without any userspace changes and all should work the same.
Why make new kernel users change userspace tools at all?
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-18 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250817141818.2370452-1-sashal@kernel.org>
2025-08-18 1:03 ` Patch "md: call del_gendisk in control path" has been added to the 6.6-stable tree Yu Kuai
2025-08-18 5:55 ` Greg KH
2025-08-18 6:26 ` Yu Kuai
2025-08-18 6:38 ` Greg KH [this message]
2025-08-18 7:13 ` Yu Kuai
2025-08-18 9:39 ` Greg KH
2025-08-19 1:06 ` Yu Kuai
2025-08-19 6:12 ` 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=2025081804-gloater-brought-c097@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=song@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xni@redhat.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;
as well as URLs for NNTP newsgroup(s).