public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d988dc155e740d76a331@syzkaller.appspotmail.com>
To: hsiangkao@linux.alibaba.com, linux-erofs@lists.ozlabs.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [erofs?] KASAN: use-after-free Read in z_erofs_transform_plain (2)
Date: Tue, 24 Feb 2026 06:46:03 -0800	[thread overview]
Message-ID: <699db9ab.050a0220.3601f3.007c.GAE@google.com> (raw)
In-Reply-To: <9fab8428-73f4-44b6-afd6-31271dcdd378@linux.alibaba.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+d988dc155e740d76a331@syzkaller.appspotmail.com
Tested-by: syzbot+d988dc155e740d76a331@syzkaller.appspotmail.com

Tested on:

commit:         f5436aa3 erofs: fix interlaced plain identification fo..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev-test
console output: https://syzkaller.appspot.com/x/log.txt?x=16a8a394580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d91443204e48b7a1
dashboard link: https://syzkaller.appspot.com/bug?extid=d988dc155e740d76a331
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2026-02-24 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  7:45 [syzbot] [erofs?] KASAN: use-after-free Read in z_erofs_transform_plain (2) syzbot
2026-02-24 10:31 ` [PATCH] erofs: fix interlaced plain identification for encoded extents Gao Xiang
2026-02-24 14:22 ` [syzbot] [erofs?] KASAN: use-after-free Read in z_erofs_transform_plain (2) Gao Xiang
2026-02-24 14:46   ` syzbot [this message]

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=699db9ab.050a0220.3601f3.007c.GAE@google.com \
    --to=syzbot+d988dc155e740d76a331@syzkaller.appspotmail.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.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