From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+7748c5375dc20dfdb92f@syzkaller.appspotmail.com>
Cc: bp@alien8.de, hpa@zytor.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk, x86@kernel.org
Subject: Re: BUG: sleeping function called from invalid context in do_user_addr_fault
Date: Tue, 7 Jul 2020 13:24:04 -0700 [thread overview]
Message-ID: <20200707202404.GA3426938@gmail.com> (raw)
In-Reply-To: <0000000000006dbe1005a9dfaa7c@google.com>
On Tue, Jul 07, 2020 at 01:16:25PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: 7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14ed01a3100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=183dd243398ba7ec
> dashboard link: https://syzkaller.appspot.com/bug?extid=7748c5375dc20dfdb92f
> compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1469d28f100000
>
The reproducer uses ioctl$FBIOPUT_VSCREENINFO on /dev/fb0, which is generating
lots of other syzbot reports. This is probably another duplicate.
See https://lkml.kernel.org/lkml/000000000000ff323f05a053100c@google.com/T/#u
for some previous discussion.
next prev parent reply other threads:[~2020-07-07 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 10:07 BUG: sleeping function called from invalid context in do_user_addr_fault syzbot
2020-07-07 20:16 ` syzbot
2020-07-07 20:24 ` Eric Biggers [this message]
2020-09-02 21:41 ` 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=20200707202404.GA3426938@gmail.com \
--to=ebiggers@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+7748c5375dc20dfdb92f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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.