WARNING in cramfs_kill_sb (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 65afe34ac33d Linux 4.14.301
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15acb207880000
kernel config: https://syzkaller.appspot.com/x/.config?x=5dfc73e3d697d68d
dashboard link: https://syzkaller.appspot.com/bug?extid=327b33251b6506f46e4b
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cba1bf735bc1/disk-65afe34a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/640415e88522/vmlinux-65afe34a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8c2d360d5af4/bzImage-65afe34a.xz

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

generic_file_write_iter+0x36f/0x650 mm/filemap.c:3208
call_write_iter include/linux/fs.h:1780 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x44c/0x630 fs/read_write.c:482
vfs_write+0x17f/0x4d0 fs/read_write.c:544
------------[ cut here ]------------
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xf2/0x210 fs/read_write.c:582
WARNING: CPU: 0 PID: 13561 at fs/super.c:1163 kill_block_super+0xbe/0xe0 fs/super.c:1163
Kernel panic - not syncing: panic_on_warn set ...

do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fba2a3e0e5f
RSP: 002b:00007fba289a0f10 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fba2a3e0e5f
RDX: 0000000001000000 RSI: 00007fba20581000 RDI: 0000000000000004
RBP: 00007fba20581000 R08: 0000000000000000 R09: 00000000000050de
R10: 0000000001000000 R11: 0000000000000293 R12: 0000000000000000
R13: 00007fba289a0fdc R14: 00007fba289a0fe0 R15: 00000000200051c2
CPU: 0 PID: 13561 Comm: syz-executor.5 Not tainted 4.14.301-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:kill_block_super+0xbe/0xe0 fs/super.c:1163
RSP: 0018:ffff88805a71fbb0 EFLAGS: 00010246
RAX: 0000000000040000 RBX: 0000000000000000 RCX: ffffc900069b9000
RDX: 0000000000040000 RSI: ffffffff818779fe RDI: ffff88809033dd30
RBP: ffff888059910600 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: ffff88809c5b4300 R12: ffff88809033d880
R13: ffffffff890a3cb0 R14: ffffffff88f45bc0 R15: dffffc0000000000
cramfs_kill_sb+0x38/0x50 fs/cramfs/inode.c:247
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
sget_userns+0x9c4/0xc10 fs/super.c:537
sget+0xd1/0x110 fs/super.c:572
mount_bdev+0xcd/0x360 fs/super.c:1107
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2572 [inline]
do_mount+0xe65/0x2a30 fs/namespace.c:2905
SYSC_mount fs/namespace.c:3121 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3098
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f0bd704d60a
RSP: 002b:00007f0bd55bdf88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000140 RCX: 00007f0bd704d60a
RDX: 0000000020000140 RSI: 0000000020000180 RDI: 00007f0bd55bdfe0
RBP: 00007f0bd55be020 R08: 00007f0bd55be020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000140
R13: 0000000020000180 R14: 00007f0bd55bdfe0 R15: 00000000200001c0
CPU: 1 PID: 13578 Comm: syz-executor.2 Not tainted 4.14.301-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold+0x10a/0x149 lib/fault-inject.c:149
should_fail_alloc_page mm/page_alloc.c:2898 [inline]
prepare_alloc_pages mm/page_alloc.c:4165 [inline]
__alloc_pages_nodemask+0x21e/0x2900 mm/page_alloc.c:4213
alloc_pages_current+0x155/0x260 mm/mempolicy.c:2107
alloc_pages include/linux/gfp.h:520 [inline]
pte_alloc_one+0x15/0x100 arch/x86/mm/pgtable.c:30
do_huge_pmd_anonymous_page+0x500/0x1700 mm/huge_memory.c:692
create_huge_pmd mm/memory.c:4002 [inline]
__handle_mm_fault+0x2ac4/0x4620 mm/memory.c:4205
handle_mm_fault+0x455/0x9c0 mm/memory.c:4271
__do_page_fault+0x549/0xad0 arch/x86/mm/fault.c:1442
page_fault+0x45/0x50 arch/x86/entry/entry_64.S:1126
RIP: e3b04700:0x1
RSP: e3b04660:0000000000000102 EFLAGS: 7f0de3b04670
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.