From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+95910cea1a7ad8850a0f@syzkaller.appspotmail.com>
Cc: bp@alien8.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
luto@kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in __syscall_return_slowpath
Date: Mon, 29 Jun 2020 09:42:27 -0700 [thread overview]
Message-ID: <20200629164227.GB1752982@gmail.com> (raw)
In-Reply-To: <00000000000077c48b05a93b96fa@google.com>
On Mon, Jun 29, 2020 at 09:31:16AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 4e99b321 Merge tag 'nfs-for-5.8-2' of git://git.linux-nfs...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=116abdd3100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=bf3aec367b9ab569
> dashboard link: https://syzkaller.appspot.com/bug?extid=95910cea1a7ad8850a0f
> compiler: gcc (GCC) 10.1.0-syz 20200507
> userspace arch: i386
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17020755100000
Looks like ioctl$FBIOPUT_VSCREENINFO on /dev/fb0 striking again. There are like
20-30 open syzbot reports for this.
See https://lkml.kernel.org/lkml/000000000000ff323f05a053100c@google.com/T/#u
for some previous discussion.
#syz dup: general protection fault in syscall_return_slowpath
prev parent reply other threads:[~2020-06-29 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 16:31 BUG: unable to handle kernel NULL pointer dereference in __syscall_return_slowpath syzbot
2020-06-29 16:42 ` Eric Biggers [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=20200629164227.GB1752982@gmail.com \
--to=ebiggers@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+95910cea1a7ad8850a0f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.