lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 02 Dec 2019 11:55:09 -0800 From: syzbot <syzbot+c792a994cd965b2ac623@...kaller.appspotmail.com> To: andriin@...com, ast@...nel.org, axboe@...nel.dk, bpf@...r.kernel.org, daniel@...earbox.net, kafai@...com, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, songliubraving@...com, syzkaller-bugs@...glegroups.com, yhs@...com Subject: WARNING in corrupted (2) 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@...kaller.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@...glegroups.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
Powered by blists - more mailing lists