From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+787bcbef9b5fec61944b@syzkaller.appspotmail.com>
Cc: alexander.levin@microsoft.com, davem@davemloft.net,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, mchehab+samsung@kernel.org,
paulmck@linux.ibm.com, syzkaller-bugs@googlegroups.com,
valdis.kletnieks@vt.edu
Subject: Re: WARNING in bdev_read
Date: Mon, 18 Nov 2019 21:44:25 -0800 [thread overview]
Message-ID: <20191119054425.GO163020@sol.localdomain> (raw)
In-Reply-To: <00000000000073309e05951e2dc1@google.com>
On Thu, Oct 17, 2019 at 10:02:07AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: bc88f85c kthread: make __kthread_queue_delayed_work static
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14e25608e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e0ac4d9b35046343
> dashboard link: https://syzkaller.appspot.com/bug?extid=787bcbef9b5fec61944b
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=159fd353600000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e82173600000
>
> The bug was bisected to:
>
> commit c48c9f7ff32b8b3965a08e40eb6763682d905b5d
> Author: Valdis Klētnieks <valdis.kletnieks@vt.edu>
> Date: Wed Aug 28 16:08:17 2019 +0000
>
> staging: exfat: add exfat filesystem code to staging
This bisection looks correct.
On a related topic: it seems the exfat filesystem is missing a mailing list.
- Eric
prev parent reply other threads:[~2019-11-19 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 17:02 syzbot
2019-11-19 5:44 ` 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=20191119054425.GO163020@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=alexander.levin@microsoft.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=syzbot+787bcbef9b5fec61944b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=valdis.kletnieks@vt.edu \
/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
all inboxes | Powered by JetHome®