From: syzbot <syzbot+3db80bbf66b88d68af9d@syzkaller.appspotmail.com>
To: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, rkovhaev@gmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in __lookup_slow
Date: Fri, 08 Jan 2021 23:20:08 -0800 [thread overview]
Message-ID: <000000000000b4098905b872801e@google.com> (raw)
In-Reply-To: <000000000000b0bbc905b05ab8d5@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=111480e7500000
start commit: a68a0262 mm/madvise: remove racy mm ownership check
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e597c2b53c984cd8
dashboard link: https://syzkaller.appspot.com/bug?extid=3db80bbf66b88d68af9d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1737b8a7500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1697246b500000
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
next prev parent reply other threads:[~2021-01-09 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:36 BUG: unable to handle kernel NULL pointer dereference in __lookup_slow syzbot
2020-12-10 4:34 ` syzbot
2021-01-09 7:20 ` syzbot [this message]
2021-01-11 11:14 ` Dmitry Vyukov
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=000000000000b4098905b872801e@google.com \
--to=syzbot+3db80bbf66b88d68af9d@syzkaller.appspotmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkovhaev@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.