linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+d7c218ea1def103f6bcd@syzkaller.appspotmail.com>
To: brauner@kernel.org, chengzhihao1@huawei.com, dev@elkcl.ru,
	 dwmw2@infradead.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	richard@nod.at,  syzkaller-bugs@googlegroups.com,
	walmeida@microsoft.com
Subject: Re: [syzbot] [jffs2?] KASAN: slab-out-of-bounds Read in jffs2_sum_add_kvec
Date: Thu, 04 Jul 2024 07:03:02 -0700	[thread overview]
Message-ID: <000000000000b4fe57061c6c6774@google.com> (raw)
In-Reply-To: <00000000000093a8ec0615b682a9@google.com>

syzbot suspects this issue was fixed by commit:

commit c6854e5a267c28300ff045480b5a7ee7f6f1d913
Author: Ilya Denisyev <dev@elkcl.ru>
Date:   Fri Apr 12 15:53:54 2024 +0000

    jffs2: prevent xattr node from overflowing the eraseblock

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12204ae1980000
start commit:   fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=aef2a55903e5791c
dashboard link: https://syzkaller.appspot.com/bug?extid=d7c218ea1def103f6bcd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1309ca57180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15f9afeb180000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: jffs2: prevent xattr node from overflowing the eraseblock

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

      reply	other threads:[~2024-07-04 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10  4:31 [syzbot] [jffs2?] KASAN: slab-out-of-bounds Read in jffs2_sum_add_kvec syzbot
2024-07-04 14:03 ` 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=000000000000b4fe57061c6c6774@google.com \
    --to=syzbot+d7c218ea1def103f6bcd@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=chengzhihao1@huawei.com \
    --cc=dev@elkcl.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=walmeida@microsoft.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;
as well as URLs for NNTP newsgroup(s).