From: syzbot <syzbot+83827f9a59abe148bff4@syzkaller.appspotmail.com>
To: agk@redhat.com, diasyzhang@tencent.com, diasyzhangqing@gmail.com,
dm-devel@redhat.com, drifabdelmalekmohamedsaid@gmail.com,
hackerowskiy@gmail.com, igorpetindev@gmail.com,
linux-kernel@vger.kernel.org, mpatocka@redhat.com,
snitzer@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dm?] KASAN: slab-use-after-free Read in pool_ctr
Date: Tue, 27 Oct 2026 06:11:03 -0700 [thread overview]
Message-ID: <6ae0a2e7.985912ea.1e5798.00c2.GAE@google.com> (raw)
In-Reply-To: <20261027122526.281548-1-diasyzhang@tencent.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+83827f9a59abe148bff4@syzkaller.appspotmail.com
Tested-by: syzbot+83827f9a59abe148bff4@syzkaller.appspotmail.com
Tested on:
commit: d135ab45 Merge tag 'backlight-next-7.4' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1595102d580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c899018ccfbe890a
dashboard link: https://syzkaller.appspot.com/bug?extid=83827f9a59abe148bff4
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1311fb0d580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-10-27 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 10:27 [PATCH] dm thin: reject metadata and data device aliases Eduard Zateev
2026-10-26 22:40 ` Mikulas Patocka
2026-10-27 12:25 ` [PATCH] dm: preserve outstanding device references across mode upgrades Qing Zhang
2026-10-27 13:11 ` syzbot [this message]
[not found] <20261027122202.279516-1-diasyzhang@tencent.com>
2026-10-27 12:47 ` [syzbot] [dm?] KASAN: slab-use-after-free Read in pool_ctr syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-10-26 2:06 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=6ae0a2e7.985912ea.1e5798.00c2.GAE@google.com \
--to=syzbot+83827f9a59abe148bff4@syzkaller.appspotmail.com \
--cc=agk@redhat.com \
--cc=diasyzhang@tencent.com \
--cc=diasyzhangqing@gmail.com \
--cc=dm-devel@redhat.com \
--cc=drifabdelmalekmohamedsaid@gmail.com \
--cc=hackerowskiy@gmail.com \
--cc=igorpetindev@gmail.com \
--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®