tree f01f46aa18ff4dbfc76483087ef85974efcbf8c2
parent b610eff230f2ce92fd48502d71ad0993792f73d3
author Jens Axboe <axboe@kernel.dk> 1652735151 +0200
committer Akilesh Kailash <akailash@google.com> 1654100127 +0000

UPSTREAM: io_uring: always use original task when preparing req identity

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.

Bug: 233078742
Reported-by: Kyle Zeng <zengyhkyle@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Akilesh Kailash <akailash@google.com>
(cherry picked from commit 29f077d070519a88a793fbc70f1e6484dc6d9e35
 from linux-5.10.y stable branch)
Change-Id: I4cc543950a95e1df201fa9867c5e9c272fd54b6f