WARNING in corrupted (2)

18 views
Skip to first unread message

syzbot

unread,
Dec 2, 2019, 2:55:10 PM12/2/19
to and...@fb.com, a...@kernel.org, ax...@kernel.dk, b...@vger.kernel.org, dan...@iogearbox.net, ka...@fb.com, linux...@vger.kernel.org, linux-...@vger.kernel.org, net...@vger.kernel.org, songliu...@fb.com, syzkall...@googlegroups.com, y...@fb.com
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+c792a9...@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 syzk...@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

Eric Biggers

unread,
Jun 28, 2020, 1:00:56 PM6/28/20
to syzbot, syzkall...@googlegroups.com
On Mon, Dec 02, 2019 at 11:55:09AM -0800, syzbot wrote:
> 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+c792a9...@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
>
>

#syz dup: WARNING in generic_make_request_checks (2)
Reply all
Reply to author
Forward
0 new messages