From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Hillf Danton <hdanton@sina.com>,
syzbot <syzbot+0e37e9d19bded16b8ab9@syzkaller.appspotmail.com>,
chuck.lever@oracle.com, LKML <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: BUG: unable to handle kernel paging request in rb_erase
Date: Fri, 26 Jun 2020 12:47:27 -0400 [thread overview]
Message-ID: <20200626164727.GB3565@fieldses.org> (raw)
In-Reply-To: <CACT4Y+b_byN4xT+-42M6XtHv=QKRrgD2aSH+Hd0CDJ=v+OYWPA@mail.gmail.com>
On Fri, Jun 26, 2020 at 12:32:42PM +0200, Dmitry Vyukov wrote:
> So far this crash happened only once:
> https://syzkaller.appspot.com/bug?extid=0e37e9d19bded16b8ab9
>
> For continuous fuzzing on syzbot it usually means either (1) it's a
> super narrow race or (2) it's a previous unnoticed memory corruption.
>
> Simpler bugs usually have much higher hit counts:
> https://syzkaller.appspot.com/upstream
> https://syzkaller.appspot.com/upstream/fixed
>
> If you did a reasonable looking for any obvious bugs in the code that
> would lead to such failure, it can make sense to postpone any
> additional actions until we have more info.
> If no info comes, at some point syzbot will auto-obsolete it, and then
> then we can assume it was (2).
OK, thanks.
It's a big heavily used data structure, if there was random memory
corruption then I guess this wouldn't be a surprising way for it to show
up.
--b.
prev parent reply other threads:[~2020-06-26 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 6:59 BUG: unable to handle kernel paging request in rb_erase syzbot
2020-06-02 21:55 ` J. Bruce Fields
[not found] ` <20200603043435.13820-1-hdanton@sina.com>
2020-06-03 14:43 ` J. Bruce Fields
2020-06-03 16:48 ` J. Bruce Fields
[not found] ` <20200604035359.2516-1-hdanton@sina.com>
2020-06-04 21:58 ` J. Bruce Fields
2020-06-25 21:02 ` J. Bruce Fields
2020-06-26 10:32 ` Dmitry Vyukov
2020-06-26 16:47 ` J. Bruce Fields [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=20200626164727.GB3565@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dvyukov@google.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=syzbot+0e37e9d19bded16b8ab9@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).