From: GuoYong Zheng <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected],
GuoYong Zheng <[email protected]>
Subject: [PATCH] io_uring: remove redundant tap space
Date: Wed, 5 Jan 2022 18:13:05 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
When show fdinfo, SqMask follow two tap space, Inconsistent with
other paras, remove one.
Signed-off-by: GuoYong Zheng <[email protected]>
---
fs/io_uring.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/io_uring.c b/fs/io_uring.c
index e6fb1bb..78a6181 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -10553,7 +10553,7 @@ static __cold void __io_uring_show_fdinfo(struct io_ring_ctx *ctx,
* and sq_tail and cq_head are changed by userspace. But it's ok since
* we usually use these info when it is stuck.
*/
- seq_printf(m, "SqMask:\t\t0x%x\n", sq_mask);
+ seq_printf(m, "SqMask:\t0x%x\n", sq_mask);
seq_printf(m, "SqHead:\t%u\n", sq_head);
seq_printf(m, "SqTail:\t%u\n", sq_tail);
seq_printf(m, "CachedSqHead:\t%u\n", ctx->cached_sq_head);
--
1.8.3.1
next reply other threads:[~2022-01-05 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 10:13 GuoYong Zheng [this message]
2022-01-05 19:32 ` [PATCH] io_uring: remove redundant tap space Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1641377585-1891-1-git-send-email-zhenggy@chinatelecom.cn \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox