From: syzbot <syzbot+listc84b10870f589e14c482@syzkaller.appspotmail.com>
To: agk@redhat.com, bmarzins@redhat.com, dm-devel@lists.linux.dev,
linux-kernel@vger.kernel.org, mpatocka@redhat.com,
snitzer@kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly dm report (Nov 2026)
Date: Fri, 13 Nov 2026 12:33:45 -0800 [thread overview]
Message-ID: <6af77429.fe96acdb.12252b.000a.GAE@google.com> (raw)
Hello dm maintainers/developers,
This is a 31-day syzbot report for the dm subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/dm
During the period, 6 new issues were detected and 0 were fixed.
In total, 6 issues are still open and 3 have already been fixed.
There are also 5 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 646 Yes KASAN: slab-use-after-free Read in snapshot_ctr
https://syzkaller.appspot.com/bug?extid=8e6fc64255334ccf3ab3
<2> 479 Yes KASAN: null-ptr-deref Read in dm_kcopyd_client_destroy
https://syzkaller.appspot.com/bug?extid=a2626a25eb2595e3ec3c
<3> 26 Yes KASAN: slab-use-after-free Read in pool_ctr
https://syzkaller.appspot.com/bug?extid=83827f9a59abe148bff4
---
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:[~2026-11-13 20:33 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=6af77429.fe96acdb.12252b.000a.GAE@google.com \
--to=syzbot+listc84b10870f589e14c482@syzkaller.appspotmail.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.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
all inboxes | Powered by JetHome®