path: root/fs/io_uring.c
diff options
authorJens Axboe <>2020-01-08 18:55:15 -0700
committerJens Axboe <>2020-01-20 17:04:06 -0700
commit354420f705ccd0aa2d41249f3bb55b4afbed1873 (patch)
tree63b8ff137f339c4bc96008548398e3b53c6b109a /fs/io_uring.c
parentcebdb98617ae3e842c81c73758a185248b37cfd6 (diff)
io_uring: add opcode to issue trace event
For some test apps at least, user_data is just zeroes. So it's not a good way to tell what the command actually is. Add the opcode to the issue trace point. Signed-off-by: Jens Axboe <>
Diffstat (limited to 'fs/io_uring.c')
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/io_uring.c b/fs/io_uring.c
index 0b30b0cf8af5..50233efd9445 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -4810,7 +4810,8 @@ static int io_submit_sqes(struct io_ring_ctx *ctx, unsigned int nr,
req->has_user = *mm != NULL;
req->in_async = async;
req->needs_fixed_file = async;
- trace_io_uring_submit_sqe(ctx, req->user_data, true, async);
+ trace_io_uring_submit_sqe(ctx, req->opcode, req->user_data,
+ true, async);
if (!io_submit_sqe(req, sqe, statep, &link))