From: syzbot <syzbot+c792a994cd965b2ac623@syzkaller.appspotmail.com>
To: andriin@fb.com, ast@kernel.org, axboe@kernel.dk,
bpf@vger.kernel.org, daniel@iogearbox.net, kafai@fb.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: WARNING in corrupted (2)
Date: Mon, 02 Dec 2019 11:55:09 -0800 [thread overview]
Message-ID: <000000000000fa5c3d0598bdf44e@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: a6ed68d6 Merge tag 'drm-next-2019-11-27' of git://anongit...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=173ab832e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6349516b24252b37
dashboard link: https://syzkaller.appspot.com/bug?extid=c792a994cd965b2ac623
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=106bdb86e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+c792a994cd965b2ac623@syzkaller.appspotmail.com
------------[ cut here ]------------
generic_make_request: Trying to write to read-only block-device loop0
(partno 0)
WARNING: CPU: 1 PID: 8854 at block/blk-core.c:800 bio_check_ro
block/blk-core.c:800 [inline]
WARNING: CPU: 1 PID: 8854 at block/blk-core.c:800
generic_make_request_checks+0x1c78/0x2190 block/blk-core.c:901
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8854 Comm: blkid Not tainted 5.4.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2019-12-02 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000fa5c3d0598bdf44e@google.com \
--to=syzbot+c792a994cd965b2ac623@syzkaller.appspotmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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).