[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191106001839.GB1450@redsun51.ssa.fujisawa.hgst.com>
Date: Wed, 6 Nov 2019 09:18:39 +0900
From: Keith Busch <kbusch@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Christoph Hellwig <hch@....de>,
Marta Rybczynska <mrybczyn@...ray.eu>,
Charles Machalow <csm10495@...il.com>,
linux-nvme <linux-nvme@...ts.infradead.org>,
axboe <axboe@...com>, Sagi Grimberg <sagi@...mberg.me>,
linux-kernel <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org
Subject: Re: [PATCH] nvme: change nvme_passthru_cmd64 to explicitly mark rsvd
On Tue, Nov 05, 2019 at 07:08:36PM -0500, Sasha Levin wrote:
> On Tue, Nov 05, 2019 at 04:31:44PM +0100, Christoph Hellwig wrote:
> > On Tue, Nov 05, 2019 at 08:39:12AM +0100, Marta Rybczynska wrote:
> > > Looks good to me. However, please note that the new ioctl made it already to 5.3.8.
> >
> > It wasn't in 5.3, but it seems like you are right and it somehow got
> > picked for the stable releases.
> >
> > Sasha, can you please revert 76d609da9ed1cc0dc780e2b539d7b827ce28f182
> > in 5.3-stable ASAP and make sure crap like backporting new ABIs that
> > haven't seen a release yet is never ever going to happen again?
>
> Sure, I'll revert it. I guess I wasn't expecting to see something like
> this in a -rc release. How did it make it into one if it's not a fix?
It is a fix, but it wasn't marked as such in the original changelog.
I've adjusted it for the pull request, currently staged here:
https://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=0d6eeb1fd625272bd60d25f2d5e116cf582fc7dc
Still, a new ioctl seems pretty aggressive for stable bot, yeah?
Powered by blists - more mailing lists