From: syzbot <syzbot+list003bd56f9e8b27f9d049@syzkaller.appspotmail.com>
To: hch@lst.de, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, sagi@grimberg.me,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nvme report (Sep 2026)
Date: Tue, 22 Sep 2026 21:33:32 -0700 [thread overview]
Message-ID: <6ab3569c.514bccd6.255447.0023.GAE@google.com> (raw)
Hello nvme maintainers/developers,
This is a 31-day syzbot report for the nvme subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/nvme
During the period, 2 new issues were detected and 0 were fixed.
In total, 3 issues are still open and 3 have already been fixed.
There are also 2 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1 No WARNING: bad unlock balance in nvme_update_ns_info
https://syzkaller.appspot.com/bug?extid=64bc2169c92ee55ad31f
<2> 2 Yes KASAN: slab-use-after-free Read in nvmet_port_subsys_allow_link
https://syzkaller.appspot.com/bug?extid=b0996ac2197dd7420c3e
<3> 1 No KASAN: slab-use-after-free Read in fcloop_t2h_xmt_ls_rsp
https://syzkaller.appspot.com/bug?extid=2a31ef5d37a9d722e987
---
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.
next reply other threads:[~2026-09-23 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 4:33 syzbot [this message]
2026-09-25 14:22 ` [syzbot] Monthly nvme report (Sep 2026) Maurizio Lombardi
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=6ab3569c.514bccd6.255447.0023.GAE@google.com \
--to=syzbot+list003bd56f9e8b27f9d049@syzkaller.appspotmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--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.