diff options
author | Usama Arif <usama.arif@bytedance.com> | 2022-02-04 15:51:13 +0100 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2022-03-10 14:32:49 +0100 |
commit | 2757be22c0f4c06d359f802fa1fc57286fa26975 (patch) | |
tree | fd4add251b29a2a7644be4a17c2f78b0d92830a5 /fs | |
parent | Linux 5.17-rc7 (diff) | |
download | linux-2757be22c0f4c06d359f802fa1fc57286fa26975.tar.xz linux-2757be22c0f4c06d359f802fa1fc57286fa26975.zip |
io_uring: remove trace for eventfd
The information on whether eventfd is registered is not very useful and
would result in the tracepoint being enclosed in an rcu_readlock in a
later patch that tries to avoid ring quiesce for registering eventfd.
Suggested-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Usama Arif <usama.arif@bytedance.com>
Link: https://lore.kernel.org/r/20220204145117.1186568-2-usama.arif@bytedance.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs')
-rw-r--r-- | fs/io_uring.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/io_uring.c b/fs/io_uring.c index 4715980e9015..8bddfacc3382 100644 --- a/fs/io_uring.c +++ b/fs/io_uring.c @@ -11179,8 +11179,7 @@ SYSCALL_DEFINE4(io_uring_register, unsigned int, fd, unsigned int, opcode, mutex_lock(&ctx->uring_lock); ret = __io_uring_register(ctx, opcode, arg, nr_args); mutex_unlock(&ctx->uring_lock); - trace_io_uring_register(ctx, opcode, ctx->nr_user_files, ctx->nr_user_bufs, - ctx->cq_ev_fd != NULL, ret); + trace_io_uring_register(ctx, opcode, ctx->nr_user_files, ctx->nr_user_bufs, ret); out_fput: fdput(f); return ret; |