From: syzbot <syzbot+5184326923f180b9d11a@syzkaller.appspotmail.com>
To: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
rkovhaev@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] KASAN: null-ptr-deref Read in fix_nodes
Date: Sat, 23 Sep 2023 17:02:23 -0700 [thread overview]
Message-ID: <00000000000061c35a06060f8eb3@google.com> (raw)
In-Reply-To: <0000000000007fcc9c05f909f7f3@google.com>
syzbot has bisected this issue to:
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=15244cfa680000
start commit: b6dad5178cea Merge tag 'nios2_fix_v6.4' of git://git.kerne..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17244cfa680000
console output: https://syzkaller.appspot.com/x/log.txt?x=13244cfa680000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac246111fb601aec
dashboard link: https://syzkaller.appspot.com/bug?extid=5184326923f180b9d11a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10bbc887280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c9558b280000
Reported-by: syzbot+5184326923f180b9d11a@syzkaller.appspotmail.com
Fixes: d24396c5290b ("reiserfs: add check for an invalid ih_entry_count")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-24 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 6:54 [syzbot] [reiserfs?] KASAN: null-ptr-deref Read in fix_nodes syzbot
2023-05-01 14:32 ` syzbot
2023-06-15 21:25 ` syzbot
2023-09-24 0:02 ` syzbot [this message]
2024-02-23 16:46 ` 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=00000000000061c35a06060f8eb3@google.com \
--to=syzbot+5184326923f180b9d11a@syzkaller.appspotmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=rkovhaev@gmail.com \
--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