mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+3a8099322b09d8d073d1@syzkaller.appspotmail.com>
To: dwmw2@infradead.org, linux-kernel@vger.kernel.org,
	 linux-mtd@lists.infradead.org, luquijeffrey@gmail.com,
	 miquel.raynal@bootlin.com, richard@nod.at,
	sashiko-bot@kernel.org,  sashiko-reviews@lists.linux.dev,
	syzkaller-bugs@googlegroups.com,  troglobit@gmail.com
Subject: Re: [syzbot] [jffs2?] KASAN: slab-use-after-free Read in jffs2_xattr_delete_inode
Date: Sun, 18 Oct 2026 22:54:01 -0700	[thread overview]
Message-ID: <6ad5b079.7f4e89eb.3d59aa.00bd.GAE@google.com> (raw)
In-Reply-To: <6a7bfdf7.ed659fcc.23056a.007f.GAE@google.com>

syzbot has bisected this issue to:

commit 7b09acdcb944a9be6acc38ab1aa8a0ffd08871c1
Author: Joachim Wiberg <troglobit@gmail.com>
Date:   Sat Oct 9 06:09:55 2021 +0000

    mtd: block2mtd: add support for an optional custom MTD label

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14e7b13e580000
start commit:   32c52ec87d62 x86/insn-eval: Fix shadowed segment index in ..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
final oops:     https://syzkaller.appspot.com/x/report.txt?x=16e7b13e580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12e7b13e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b38d39c45202f4fa
dashboard link: https://syzkaller.appspot.com/bug?extid=3a8099322b09d8d073d1
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17684bc9580000

Reported-by: syzbot+3a8099322b09d8d073d1@syzkaller.appspotmail.com
Fixes: 7b09acdcb944 ("mtd: block2mtd: add support for an optional custom MTD label")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2026-10-19  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12  5:00 syzbot
2026-10-02 15:04 ` syzbot
2026-10-18 18:25 ` syzbot
2026-10-19  5:54 ` 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=6ad5b079.7f4e89eb.3d59aa.00bd.GAE@google.com \
    --to=syzbot+3a8099322b09d8d073d1@syzkaller.appspotmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=luquijeffrey@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=troglobit@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
all inboxes | Powered by JetHome®