summaryrefslogtreecommitdiffstats
path: root/io_uring
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2024-09-20 07:38:01 +0200
committerJens Axboe <axboe@kernel.dk>2024-09-20 08:17:46 +0200
commiteed138d67d99312f07ed3bc326903b6808885571 (patch)
tree46a215b468a7ba381094f2fef3e9eb18811fdb17 /io_uring
parentio_uring: check for presence of task_work rather than TIF_NOTIFY_SIGNAL (diff)
downloadlinux-eed138d67d99312f07ed3bc326903b6808885571.tar.xz
linux-eed138d67d99312f07ed3bc326903b6808885571.zip
io_uring: improve request linking trace
Right now any link trace is listed as being linked after the head request in the chain, but it's more useful to note explicitly which request a given new request is chained to. Change the link trace to dump the tail request so that chains are immediately apparent when looking at traces. Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'io_uring')
-rw-r--r--io_uring/io_uring.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index 11c455b638a2..d306f566a944 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -2153,7 +2153,7 @@ static inline int io_submit_sqe(struct io_ring_ctx *ctx, struct io_kiocb *req,
* conditions are true (normal request), then just queue it.
*/
if (unlikely(link->head)) {
- trace_io_uring_link(req, link->head);
+ trace_io_uring_link(req, link->last);
link->last->link = req;
link->last = req;