From: Al Viro <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected],
Linus Torvalds <[email protected]>
Subject: [RFC][PATCH] fix io_uring_show_fdinfo() misuse of ->d_iname
Date: Sat, 18 Jan 2025 02:57:17 +0000 [thread overview]
Message-ID: <20250118025717.GU1977892@ZenIV> (raw)
The output of io_uring_show_fdinfo() is crazy - for
each slot of io_uring file_table it produces either
INDEX: <none>
or
INDEX: NAME
where INDEX runs through all numbers from 0 to ctx->file_table.data.nr-1
and NAME is usually the last component of pathname of file in slot
#INDEX. Usually == if it's no longer than 39 bytes. If it's longer,
you get junk. Oh, and if it contains newlines, you get several lines and
no way to tell that it has happened, them's the breaks. If it's happens
to be /home/luser/<none>, well, what you see is indistinguishable from what
you'd get if it hadn't been there...
According to Jens, it's *not* cast in stone, so we should be able to
change that to something saner. I see two options:
1) replace NAME with actual pathname of the damn file, quoted to reasonable
extent.
2) same, and skip the INDEX: <none> lines. It's not as if they contained
any useful information - the size of table is printed right before that,
so you'd get
...
UserFiles: 16
0: foo
11: bar
UserBufs: ....
instead of
...
UserFiles: 16
0: foo
1: <none>
2: <none>
3: <none>
4: <none>
5: <none>
6: <none>
7: <none>
8: <none>
9: <none>
10: <none>
11: bar
12: <none>
13: <none>
14: <none>
15: <none>
UserBufs: ....
IMO the former is more useful for any debugging purposes.
The patch is trivial either way - (1) is
------------------------
diff --git a/io_uring/fdinfo.c b/io_uring/fdinfo.c
index b214e5a407b5..1017249ae610 100644
--- a/io_uring/fdinfo.c
+++ b/io_uring/fdinfo.c
@@ -211,10 +211,12 @@ __cold void io_uring_show_fdinfo(struct seq_file *m, struct file *file)
if (ctx->file_table.data.nodes[i])
f = io_slot_file(ctx->file_table.data.nodes[i]);
+ seq_printf(m, "%5u: ", i);
if (f)
- seq_printf(m, "%5u: %s\n", i, file_dentry(f)->d_iname);
+ seq_file_path(m, f, " \t\n\\<");
else
- seq_printf(m, "%5u: <none>\n", i);
+ seq_puts(m, "<none>");
+ seq_puts(m, "\n");
}
seq_printf(m, "UserBufs:\t%u\n", ctx->buf_table.nr);
for (i = 0; has_lock && i < ctx->buf_table.nr; i++) {
------------------------
and (2) -
------------------------
diff --git a/io_uring/fdinfo.c b/io_uring/fdinfo.c
index b214e5a407b5..f60d0a9d505e 100644
--- a/io_uring/fdinfo.c
+++ b/io_uring/fdinfo.c
@@ -211,10 +211,11 @@ __cold void io_uring_show_fdinfo(struct seq_file *m, struct file *file)
if (ctx->file_table.data.nodes[i])
f = io_slot_file(ctx->file_table.data.nodes[i]);
- if (f)
- seq_printf(m, "%5u: %s\n", i, file_dentry(f)->d_iname);
- else
- seq_printf(m, "%5u: <none>\n", i);
+ if (f) {
+ seq_printf(m, "%5u: ", i);
+ seq_file_path(m, f, " \t\n\\");
+ seq_puts(m, "\n");
+ }
}
seq_printf(m, "UserBufs:\t%u\n", ctx->buf_table.nr);
for (i = 0; has_lock && i < ctx->buf_table.nr; i++) {
------------------------
Preferences? The difference in seq_printf() argument is due to the need
to quote < in filenames if we need to distinguish them from <none>;
whitespace and \ needs to be quoted in either case.
next reply other threads:[~2025-01-18 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 2:57 Al Viro [this message]
2025-01-18 15:02 ` [RFC][PATCH] fix io_uring_show_fdinfo() misuse of ->d_iname Jens Axboe
2025-01-19 3:26 ` Al Viro
2025-01-19 14:28 ` 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=20250118025717.GU1977892@ZenIV \
[email protected] \
[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