On Wed, Jul 20, 2022 at 06:48:09AM -0600, Jens Axboe wrote:
> On 7/19/22 5:52 AM, Lee Jones wrote:
> > This issue is conceptually identical to the one fixed in 29f077d07051
> > ("io_uring: always use original task when preparing req identity"), so
> > rather than reinvent the wheel, I'm shamelessly quoting the commit
> > message from that patch - thanks Jens:
> >
> > "If the ring is setup with IORING_SETUP_IOPOLL and we have more than
> > one task doing submissions on a ring, we can up in a situation where
> > we assign the context from the current task rather than the request
> > originator.
> >
> > Always use req->task rather than assume it's the same as current.
> >
> > No upstream patch exists for this issue, as only older kernels with
> > the non-native workers have this problem."
>
> Greg, can you pick this one up for 5.10-stable? Thanks!
Now queued up, thanks.
greg k-h
