From: syzbot <syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl
Date: Fri, 01 Dec 2023 18:44:31 -0800 [thread overview]
Message-ID: <0000000000004f26a8060b7ddda2@google.com> (raw)
In-Reply-To: <00000000000047eb7e060b652d9a@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [block?] [trace?] INFO: task hung in blk_trace_ioctl
Author: eadavis@qq.com
please test task hung in blk_trace_ioctl
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 8c9660f65153
diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index 54ade89a1ad2..f5d3576ef3ed 100644
--- a/kernel/trace/blktrace.c
+++ b/kernel/trace/blktrace.c
@@ -735,7 +735,10 @@ int blk_trace_ioctl(struct block_device *bdev, unsigned cmd, char __user *arg)
int ret, start = 0;
char b[BDEVNAME_SIZE];
- mutex_lock(&q->debugfs_mutex);
+ if (cmd == BLKTRACESETUP)
+ mutex_lock(&q->debugfs_mutex);
+ else
+ mutex_lock_nested(&q->debugfs_mutex, 2);
switch (cmd) {
case BLKTRACESETUP:
next prev parent reply other threads:[~2023-12-02 2:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 21:17 [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4) syzbot
2023-12-01 8:29 ` Pengfei Xu
2023-12-02 1:25 ` [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl syzbot
2023-12-02 2:14 ` syzbot
2023-12-02 2:44 ` syzbot [this message]
2023-12-02 2:54 ` syzbot
[not found] ` <tencent_6537E04AAC74F976B567603CEB377A96FA09@qq.com>
2023-12-02 9:19 ` [PATCH next] trace/blktrace: fix " Yu Kuai
2023-12-02 22:07 ` Steven Rostedt
2023-12-03 11:45 ` Pengfei Xu
2024-10-11 19:20 ` [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl (4) Jens Axboe
2024-10-11 19:32 ` Aleksandr Nogikh
2024-10-11 19:33 ` Jens Axboe
2024-10-11 19:41 ` Aleksandr Nogikh
2024-10-11 20:43 ` Jens Axboe
2024-10-14 7:58 ` Aleksandr Nogikh
2024-10-12 1:20 ` syzbot
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=0000000000004f26a8060b7ddda2@google.com \
--to=syzbot+ed812ed461471ab17a0c@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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