[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190613091430.GA28704@kroah.com>
Date: Thu, 13 Jun 2019 11:14:30 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: Stephen Bates <sbates@...thlin.com>,
Mark Rutland <mark.rutland@....com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"shhuiw@...mail.com" <shhuiw@...mail.com>,
Logan Gunthorpe <logang@...tatee.com>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] io_uring: fix SQPOLL cpu check
On Thu, Jun 13, 2019 at 02:54:45AM -0600, Jens Axboe wrote:
> On 6/12/19 3:47 AM, Stephen Bates wrote:
> >> Aargh. My original patch [1] handled that correctly, and this case was
> >> explicitly called out in the commit message, which was retained even
> >> when the patch was "simplified". That's rather disappointing. :/
> >
> > It looks like Jens did a fix for this (44a9bd18a0f06bba
> > " io_uring: fix failure to verify SQ_AFF cpu") which is in the 5.2-rc series
> > but which hasn’t been applied to the stable series yet. I am not sure how
> > I missed that but it makes my patch redundant.
> >
> > Jens, will 44a9bd18a0f06bba be applied to stable kernels?
>
> Yes, we can get it flagged for stable. Greg, can you pull in the above
> commit for 5.1 stable?
Now snuck in for the next 5.1.y release, thanks.
greg k-h
Powered by blists - more mailing lists