[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000e952ff060b7d724d@google.com>
Date: Fri, 01 Dec 2023 18:14:46 -0800
From: syzbot <syzbot+ed812ed461471ab17a0c@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] [block?] [trace?] INFO: task hung in blk_trace_ioctl
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.
***
Subject: [block?] [trace?] INFO: task hung in blk_trace_ioctl
Author: eadavis@...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..a1b341722693 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_nested(&q->debugfs_mutex, 0);
+ else
+ mutex_lock_nested(&q->debugfs_mutex, 1);
switch (cmd) {
case BLKTRACESETUP:
Powered by blists - more mailing lists