From: syzbot <syzbot+ecf51a7ccb6b1394e90c@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tristmd@gmail.com
Subject: Re: [syzbot] [jfs?] KASAN: slab-use-after-free Read in lbmIODone
Date: Fri, 17 Apr 2026 12:58:01 -0700 [thread overview]
Message-ID: <69e290c9.a00a0220.1bd0ca.0025.GAE@google.com> (raw)
In-Reply-To: <177645401243.291533.1310891472323715606@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ecf51a7ccb6b1394e90c@syzkaller.appspotmail.com
Tested-by: syzbot+ecf51a7ccb6b1394e90c@syzkaller.appspotmail.com
Tested on:
commit: 59bd5ae0 Merge tag 'for-v7.1' of git://git.kernel.org/..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=17748fca580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b44c9b54cc2c4033
dashboard link: https://syzkaller.appspot.com/bug?extid=ecf51a7ccb6b1394e90c
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=17864702580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-04-17 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177645401243.291533.1310891472323715606@gmail.com>
2026-04-17 19:58 ` syzbot [this message]
[not found] <177644292572.3792638.6921571003846559600@talencesecurity.com>
2026-04-17 18:36 ` [syzbot] [jfs?] KASAN: slab-use-after-free Read in lbmIODone syzbot
[not found] <20260417142003.3369860-1-tristmd@gmail.com>
2026-04-17 16:37 ` syzbot
2025-09-29 13:20 syzbot
2026-04-15 6:59 ` syzbot
2026-04-15 9:06 ` syzbot
2026-04-17 12:41 ` Edward Adam Davis
2026-04-17 12:59 ` 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=69e290c9.a00a0220.1bd0ca.0025.GAE@google.com \
--to=syzbot+ecf51a7ccb6b1394e90c@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tristmd@gmail.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