io_uring: Use original task for req identity in io_identity_cow()
This issue is conceptually identical to the one fixed in 29f077d0 ("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." Cc: Jens Axboe <axboe@kernel.dk> Cc: Pavel Begunkov <asml.silence@gmail.com> Cc: Alexander Viro <viro@zeniv.linux.org.uk> Cc: io-uring@vger.kernel.org Cc: linux-fsdevel@vger.kernel.org Fixes: 5c3462cf ("io_uring: store io_identity in io_uring_task") Signed-off-by:Lee Jones <lee@kernel.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Loading
-
mentioned in commit f0fe4f76
-
mentioned in commit 0380da7f
-
mentioned in commit 6522bf85
-
mentioned in commit 37d2d642
-
mentioned in commit 30d3caba
-
mentioned in commit 5a7c3f60
-
mentioned in commit 77a735fe
-
mentioned in commit 1523779a
-
mentioned in commit daee40c3
-
mentioned in commit d8393948
-
mentioned in commit eb34c25d
-
mentioned in commit 673c21e8
-
mentioned in commit 9ab400c0
Please sign in to comment