From: Song Liu <song@kernel.org>
To: Christoph Hellwig <hch@lst.de>,
linux-raid <linux-raid@vger.kernel.org>,
Li Nan <linan666@huaweicloud.com>
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 5.10 033/238] md: implement ->set_read_only to hook into BLKROSET processing
Date: Tue, 26 Mar 2024 01:46:40 -0700 [thread overview]
Message-ID: <CAPhsuW7FREFLrAnt2iYDRoJG0d=OXm-5vy3OCJ7MOJDp2SE9GQ@mail.gmail.com> (raw)
In-Reply-To: <20240326074029.GB9773@lst.de>
Hi Li Nan,
Could you please look into this (back port 9674f54e41ff to older stable
kernels)? If there is no clean back port, I would recommend we not do
the back port.
Thanks,
Song
On Tue, Mar 26, 2024 at 12:40 AM Christoph Hellwig <hch@lst.de> wrote:
>
> On Mon, Mar 25, 2024 at 07:26:43AM -0400, Sasha Levin wrote:
> > On Mon, Mar 25, 2024 at 02:04:35AM +0100, Christoph Hellwig wrote:
> >> How did we end up backporting all these block layer API changes?
> >
> > They were brought in as a dependency for 9674f54e41ff ("md: Don't clear
> > MD_CLOSING when the raid is about to stop").
> >
> > It's possible to work around bringing them during backport, but I
> > preferred to bring the dependencies instead.
>
> I really don't see what these giant backports bring us. If people
> want all the changes they'd just be better off on a modern kernel
> rather than these frankenkernels. The automatic backporting is
> gettind way out of hand. If the MD maintainers want
> 9674f54e41ff, maybe they can send a tailor made backport?
next parent reply other threads:[~2024-03-26 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240324234027.1354210-1-sashal@kernel.org>
[not found] ` <20240324234027.1354210-34-sashal@kernel.org>
[not found] ` <20240325010435.GA23652@lst.de>
[not found] ` <ZgFfc2b6VsX_QSu4@sashalap>
[not found] ` <20240326074029.GB9773@lst.de>
2024-03-26 8:46 ` Song Liu [this message]
2024-03-27 1:18 ` [PATCH 5.10 033/238] md: implement ->set_read_only to hook into BLKROSET processing Li Nan
2024-03-27 5:50 ` Song Liu
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='CAPhsuW7FREFLrAnt2iYDRoJG0d=OXm-5vy3OCJ7MOJDp2SE9GQ@mail.gmail.com' \
--to=song@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linan666@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).