From: syzbot <syzbot+lista56c9771895bcef0bc37@syzkaller.appspotmail.com>
To: josef@toxicpanda.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, nbd@other.debian.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nbd report (Dec 2024)
Date: Wed, 25 Dec 2024 02:07:19 -0800 [thread overview]
Message-ID: <676bd957.050a0220.2f3838.02e2.GAE@google.com> (raw)
Hello nbd maintainers/developers,
This is a 31-day syzbot report for the nbd subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/nbd
During the period, 1 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 6 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 133 Yes INFO: task hung in nbd_queue_rq
https://syzkaller.appspot.com/bug?extid=30c16035531e3248dcbc
<2> 129 Yes INFO: task hung in nbd_ioctl (3)
https://syzkaller.appspot.com/bug?extid=fe03c50d25c0188f7487
<3> 25 No possible deadlock in __nbd_set_size
https://syzkaller.appspot.com/bug?extid=143deed0891e0c211d8f
<4> 12 No possible deadlock in __synchronize_srcu (2)
https://syzkaller.appspot.com/bug?extid=c89fbbd2838560d51069
<5> 5 No possible deadlock in nbd_set_size
https://syzkaller.appspot.com/bug?extid=966c3b607cb094ce7299
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2024-12-25 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=676bd957.050a0220.2f3838.02e2.GAE@google.com \
--to=syzbot+lista56c9771895bcef0bc37@syzkaller.appspotmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).