summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2024-09-19 23:38:01 -0600
committerJens Axboe <axboe@kernel.dk>2024-09-20 00:17:46 -0600
commiteed138d67d99312f07ed3bc326903b6808885571 (patch)
tree46a215b468a7ba381094f2fef3e9eb18811fdb17
parent04beb6e0e08c30c6f845f50afb7d7953603d7a6f (diff)
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>
-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;