Received-SPF: pass (google.com: domain of linux-kernel+bounces-118476-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Tue, 26 Mar 2024 08:40:29 +0100
From: Christoph Hellwig <hch@lst.de>
To: Sasha Levin <sashal@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Song Liu <song@kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 5.10 033/238] md: implement ->set_read_only to hook
 into BLKROSET processing
Message-ID: <20240326074029.GB9773@lst.de>
References: <20240324234027.1354210-1-sashal@kernel.org> <20240324234027.1354210-34-sashal@kernel.org> <20240325010435.GA23652@lst.de> <ZgFfc2b6VsX_QSu4@sashalap>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZgFfc2b6VsX_QSu4@sashalap>
User-Agent: Mutt/1.5.17 (2007-11-01)

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?