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. Reported-by:Kyle Zeng <zengyhkyle@gmail.com> Signed-off-by:
Jens Axboe <axboe@kernel.dk> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Loading
-
mentioned in commit 257fcb7b
-
mentioned in commit f0fe4f76
-
mentioned in commit 812805ff
-
mentioned in commit 0380da7f
-
mentioned in commit cac3a605
-
mentioned in commit cac3a605
-
mentioned in commit 6522bf85
-
mentioned in commit eb9f9532
-
mentioned in commit 37d2d642
-
mentioned in commit 0e509674
-
mentioned in commit 30d3caba
-
mentioned in commit b07e0093
-
mentioned in commit 5a7c3f60
-
mentioned in commit 701b6386
-
mentioned in commit 77a735fe
-
mentioned in commit 19c16239
-
mentioned in commit 1523779a
-
mentioned in commit 09ea593e
-
mentioned in commit daee40c3
-
mentioned in commit 011500e3
-
mentioned in commit d8393948
-
mentioned in commit 95e278bd
-
mentioned in commit eb34c25d
-
mentioned in commit 673c21e8
-
mentioned in commit 244d8bc3
-
mentioned in commit 9ab400c0
Please sign in to comment