[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6729c5f8.050a0220.2edce.1503.GAE@google.com>
Date: Mon, 04 Nov 2024 23:15:04 -0800
From: syzbot <syzbot+a3c16289c8c99b02cac1@...kaller.appspotmail.com>
To: axboe@...nel.dk, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, mathieu.desnoyers@...icios.com,
mhiramat@...nel.org, ming.lei@...hat.com, rostedt@...dmis.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [block?] [trace?] possible deadlock in blk_trace_ioctl
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a3c16289c8c99b02cac1@...kaller.appspotmail.com
Tested-by: syzbot+a3c16289c8c99b02cac1@...kaller.appspotmail.com
Tested on:
commit: 72697401 block: don't verify IO lock for freeze/unfree..
git tree: https://github.com/ming1/linux.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14e8ed5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=dfea72efa3e2aef2
dashboard link: https://syzkaller.appspot.com/bug?extid=a3c16289c8c99b02cac1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
Powered by blists - more mailing lists