All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2b5c012223e37b7c2a88@syzkaller.appspotmail.com>
To: ebiggers@google.com, jack@suse.cz, jhubbard@nvidia.com,
	junxiao.bi@oracle.com, liao.pingfang@zte.com.cn,
	linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
	rkovhaev@gmail.com, syzkaller-bugs@googlegroups.com,
	william.kucharski@oracle.com, willy@infradead.org
Subject: Re: KASAN: use-after-free Read in reiserfs_fill_super
Date: Tue, 05 Jan 2021 00:00:05 -0800	[thread overview]
Message-ID: <0000000000003ad7db05b8229802@google.com> (raw)
In-Reply-To: <000000000000b51b6b05b5dc833b@google.com>

syzbot suspects this issue was fixed by commit:

commit d24396c5290ba8ab04ba505176874c4e04a2d53c
Author: Rustam Kovhaev <rkovhaev@gmail.com>
Date:   Sun Nov 1 14:09:58 2020 +0000

    reiserfs: add check for an invalid ih_entry_count

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=113a2d57500000
start commit:   b3298500 Merge tag 'for-5.10/dm-fixes' of git://git.kernel..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=e49433cfed49b7d9
dashboard link: https://syzkaller.appspot.com/bug?extid=2b5c012223e37b7c2a88
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12ad719b500000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11193117500000

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

#syz fix: reiserfs: add check for an invalid ih_entry_count

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

  reply	other threads:[~2021-01-05  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  9:33 KASAN: use-after-free Read in reiserfs_fill_super syzbot
2021-01-05  8:00 ` syzbot [this message]
2022-07-22 20:52 Dipanjan Das

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=0000000000003ad7db05b8229802@google.com \
    --to=syzbot+2b5c012223e37b7c2a88@syzkaller.appspotmail.com \
    --cc=ebiggers@google.com \
    --cc=jack@suse.cz \
    --cc=jhubbard@nvidia.com \
    --cc=junxiao.bi@oracle.com \
    --cc=liao.pingfang@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=rkovhaev@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.