From: syzbot <syzbot+a3c16289c8c99b02cac1@syzkaller.appspotmail.com>
To: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
ming.lei@redhat.com, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [trace?] possible deadlock in blk_trace_ioctl
Date: Mon, 04 Nov 2024 23:15:04 -0800 [thread overview]
Message-ID: <6729c5f8.050a0220.2edce.1503.GAE@google.com> (raw)
In-Reply-To: <Zym_h_EYRVX18dSw@fedora>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a3c16289c8c99b02cac1@syzkaller.appspotmail.com
Tested-by: syzbot+a3c16289c8c99b02cac1@syzkaller.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.
next prev parent reply other threads:[~2024-11-05 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 18:29 [syzbot] [block?] [trace?] possible deadlock in blk_trace_ioctl syzbot
2024-11-05 6:47 ` Ming Lei
2024-11-05 7:15 ` syzbot [this message]
2024-11-05 22:46 ` Hillf Danton
2024-11-05 23:16 ` syzbot
2025-01-12 4:34 ` 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=6729c5f8.050a0220.2edce.1503.GAE@google.com \
--to=syzbot+a3c16289c8c99b02cac1@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ming.lei@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.