[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DCE71F95-F72A-414C-8A02-98CC81237F40@raithlin.com>
Date: Wed, 12 Jun 2019 09:47:40 +0000
From: "Stephen Bates" <sbates@...thlin.com>
To: Mark Rutland <mark.rutland@....com>
CC: "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>,
Jens Axboe <axboe@...nel.dk>,
"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
> 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?
Stephen
Powered by blists - more mailing lists