From: syzbot <syzbot+1930da7118e99b06e4ab@syzkaller.appspotmail.com>
To: alexander.levin@microsoft.com, davem@davemloft.net,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab@kernel.org, namjae.jeon@samsung.com,
pragat.pandya@gmail.com, syzkaller-bugs@googlegroups.com,
valdis.kletnieks@vt.edu
Subject: Re: WARNING in exfat_bdev_read
Date: Wed, 29 Apr 2020 05:12:02 -0700 [thread overview]
Message-ID: <0000000000001821b605a46cdb7f@google.com> (raw)
In-Reply-To: <00000000000051770905984d38d3@google.com>
syzbot suspects this bug was fixed by commit:
commit 5f33771fb0ac484d6e8cc34cb1e27c37442cd0db
Author: Namjae Jeon <namjae.jeon@samsung.com>
Date: Fri Jan 3 01:13:45 2020 +0000
staging: exfat: add STAGING prefix to config names
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1407f818100000
start commit: 32ef9553 Merge tag 'fsnotify_for_v5.5-rc1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ff560c3de405258c
dashboard link: https://syzkaller.appspot.com/bug?extid=1930da7118e99b06e4ab
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e208a6e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f83882e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: staging: exfat: add STAGING prefix to config names
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-04-29 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 5:25 WARNING in exfat_bdev_read syzbot
2020-04-29 12:12 ` syzbot [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=0000000000001821b605a46cdb7f@google.com \
--to=syzbot+1930da7118e99b06e4ab@syzkaller.appspotmail.com \
--cc=alexander.levin@microsoft.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=pragat.pandya@gmail.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;
as well as URLs for NNTP newsgroup(s).