WARNING in generic_make_request (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59456c9cc40c Linux 4.19.204
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16671731300000
kernel config: https://syzkaller.appspot.com/x/.config?x=a84b4514346e13dc
dashboard link: https://syzkaller.appspot.com/bug?extid=c176aa11e1e4ff0fe479
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c176aa...@syzkaller.appspotmail.com

generic_make_request: Trying to write to read-only block-device sda1 (partno 1)
should_fail_alloc_page mm/page_alloc.c:3088 [inline]
prepare_alloc_pages mm/page_alloc.c:4346 [inline]
__alloc_pages_nodemask+0x239/0x2890 mm/page_alloc.c:4393
WARNING: CPU: 1 PID: 34 at block/blk-core.c:2183 bio_check_ro block/blk-core.c:2183 [inline]
WARNING: CPU: 1 PID: 34 at block/blk-core.c:2183 blk_partition_remap block/blk-core.c:2234 [inline]
WARNING: CPU: 1 PID: 34 at block/blk-core.c:2183 generic_make_request_checks+0x1f9b/0x22e0 block/blk-core.c:2285
Kernel panic - not syncing: panic_on_warn set ...

alloc_pages_vma+0xf2/0x780 mm/mempolicy.c:2161
alloc_zeroed_user_highpage_movable include/linux/highmem.h:184 [inline]
do_anonymous_page+0x7c2/0x1be0 mm/memory.c:3312
handle_pte_fault mm/memory.c:4173 [inline]
__handle_mm_fault+0x227a/0x41c0 mm/memory.c:4299
handle_mm_fault+0x436/0xb10 mm/memory.c:4336
__do_page_fault+0x68e/0xd60 arch/x86/mm/fault.c:1412
page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1205
RIP: 0033:0x409f27
Code: c7 c0 ff ff ff ff e9 1e fc ff ff 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55 41 54 41 bc 00 00 c0 fe 55 53 48 81 ec 48 1b 00 00 <48> 89 bc 24 b8 00 00 00 4c 8d ac 24 30 07 00 00 48 89 b4 24 b0 00
RSP: 002b:00007fe237528600 EFLAGS: 00010206
RAX: 0000000000409f10 RBX: 000000000056c038 RCX: 00000000200001c0
RDX: 0000000020fe7000 RSI: ffffffffffffffff RDI: 0000000000000006
RBP: 00007fe23752a1d0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000fec00000
R13: 00007ffd2a6e250f R14: 00007fe23752a300 R15: 0000000000022000
CPU: 1 PID: 34 Comm: kworker/u4:2 Not tainted 4.19.204-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: writeback wb_workfn (flush-8:0)
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
syz-executor.2 invoked oom-killer: gfp_mask=0x0(), nodemask=(null), order=0, oom_score_adj=1000
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
syz-executor.2 cpuset=/ mems_allowed=0-1
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:bio_check_ro block/blk-core.c:2183 [inline]
RIP: 0010:blk_partition_remap block/blk-core.c:2234 [inline]
RIP: 0010:generic_make_request_checks+0x1f9b/0x22e0 block/blk-core.c:2285
Code: 2c 03 00 00 45 8b be 9c 04 00 00 48 8d 74 24 68 48 89 ef e8 f7 0c 06 00 48 c7 c7 00 28 b2 88 48 89 c6 44 89 fa e8 45 56 91 04 <0f> 0b 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1 ea 03 0f b6 04
RSP: 0018:ffff8880b50b71b8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff8880ad204000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814e0d61 RDI: ffffed1016a16e29
RBP: ffff88809ec3a180 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88809ec3a1b0
R13: ffff88809ec3a188 R14: ffff8880a8e80d40 R15: 0000000000000001
generic_make_request+0x23f/0xdf0 block/blk-core.c:2412
submit_bio+0xb1/0x430 block/blk-core.c:2576
ext4_io_submit+0x181/0x210 fs/ext4/page-io.c:356
ext4_writepages+0x1130/0x37f0 fs/ext4/inode.c:2837
do_writepages+0xe5/0x290 mm/page-writeback.c:2344
__writeback_single_inode+0x10c/0x11d0 fs/fs-writeback.c:1385
writeback_sb_inodes+0x537/0xef0 fs/fs-writeback.c:1647
__writeback_inodes_wb+0xc6/0x280 fs/fs-writeback.c:1716
wb_writeback+0x841/0xcc0 fs/fs-writeback.c:1822
wb_check_old_data_flush fs/fs-writeback.c:1924 [inline]
wb_do_writeback fs/fs-writeback.c:1977 [inline]
wb_workfn+0x8ba/0x1250 fs/fs-writeback.c:2006
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess):
0: c7 c0 ff ff ff ff mov $0xffffffff,%eax
6: e9 1e fc ff ff jmpq 0xfffffc29
b: 0f 1f 84 00 00 00 00 nopl 0x0(%rax,%rax,1)
12: 00
13: 41 57 push %r15
15: 41 56 push %r14
17: 41 55 push %r13
19: 41 54 push %r12
1b: 41 bc 00 00 c0 fe mov $0xfec00000,%r12d
21: 55 push %rbp
22: 53 push %rbx
23: 48 81 ec 48 1b 00 00 sub $0x1b48,%rsp
2a: 48 89 bc 24 b8 00 00 mov %rdi,0xb8(%rsp) <-- trapping instruction
31: 00
32: 4c 8d ac 24 30 07 00 lea 0x730(%rsp),%r13
39: 00
3a: 48 rex.W
3b: 89 .byte 0x89
3c: b4 24 mov $0x24,%ah
3e: b0 00 mov $0x0,%al


---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.