From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Stephen Bates <sbates@raithlin.com>,
Mark Rutland <mark.rutland@arm.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shhuiw@foxmail.com" <shhuiw@foxmail.com>,
Logan Gunthorpe <logang@deltatee.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] io_uring: fix SQPOLL cpu check
Date: Thu, 13 Jun 2019 11:14:30 +0200 [thread overview]
Message-ID: <20190613091430.GA28704@kroah.com> (raw)
In-Reply-To: <b3c9138e-bf3b-0851-a63e-f52f926d5ed8@kernel.dk>
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
next prev parent reply other threads:[~2019-06-13 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 23:56 [PATCH] io_uring: fix SQPOLL cpu check Stephen Bates
2019-06-12 9:24 ` Mark Rutland
2019-06-12 9:47 ` Stephen Bates
2019-06-13 8:54 ` Jens Axboe
2019-06-13 9:14 ` Greg Kroah-Hartman [this message]
2019-06-13 9:15 ` Jens Axboe
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=20190613091430.GA28704@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mark.rutland@arm.com \
--cc=sbates@raithlin.com \
--cc=shhuiw@foxmail.com \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).