[fat?] WARNING in __list_lru_init

5 views
Skip to first unread message

syzbot

unread,
Feb 8, 2023, 8:49:51 PM2/8/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a8ad60f2af58 Linux 4.14.305
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1308becb480000
kernel config: https://syzkaller.appspot.com/x/.config?x=2f23dc9802022031
dashboard link: https://syzkaller.appspot.com/bug?extid=f13eed984eb1c0bfc9db
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=133fa283480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10aa94b7480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c38348fd389d/disk-a8ad60f2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3a775d221689/vmlinux-a8ad60f2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32e71e04d2b4/bzImage-a8ad60f2.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/37e8b43750b7/mount_0.gz

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

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
------------[ cut here ]------------
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold+0x10a/0x149 lib/fault-inject.c:149
WARNING: CPU: 1 PID: 8133 at fs/super.c:1163 kill_block_super+0xbe/0xe0 fs/super.c:1163
should_failslab+0xd6/0x130 mm/failslab.c:32
Kernel panic - not syncing: kernel: panic_on_warn set ...

slab_pre_alloc_hook mm/slab.h:421 [inline]
slab_alloc mm/slab.c:3376 [inline]
__do_kmalloc mm/slab.c:3718 [inline]
__kmalloc+0x2c1/0x400 mm/slab.c:3729
kmalloc include/linux/slab.h:493 [inline]
kzalloc include/linux/slab.h:661 [inline]
__list_lru_init+0x67/0x710 mm/list_lru.c:539
alloc_super fs/super.c:229 [inline]
sget_userns+0x4e4/0xc10 fs/super.c:516
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:0x7fcbff06821a
RSP: 002b:00007ffff1344938 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fcbff06821a
RDX: 0000000020000240 RSI: 0000000020000280 RDI: 00007ffff1344950
RBP: 00007ffff1344950 R08: 00007ffff1344990 R09: 0000000000000228
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000005
R13: 00005555567b42c0 R14: 0000000000000000 R15: 00007ffff1344990
CPU: 1 PID: 8133 Comm: syz-executor313 Not tainted 4.14.305-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x21d/0x451 kernel/panic.c:247
check_panic_on_warn.cold+0x19/0x35 kernel/panic.c:171
__warn+0xdf/0x1e0 kernel/panic.c:603
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:ffff88809c6f7bc8 EFLAGS: 00010297
RAX: ffff8880aefd4080 RBX: 0000000000000000 RCX: 1ffff11015dfa926
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff8880902e6d30
RBP: ffff88809420e3c0 R08: ffffffff8b9c15a0 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880aefd4080 R12: ffff8880902e6880
R13: ffffffff890aee50 R14: ffffffff88f46340 R15: dffffc0000000000
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:0x7fcbff06821a
RSP: 002b:00007ffff1344938 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fcbff06821a
RDX: 0000000020000240 RSI: 0000000020000280 RDI: 00007ffff1344950
RBP: 00007ffff1344950 R08: 00007ffff1344990 R09: 0000000000000228
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000005
R13: 00005555567b42c0 R14: 0000000000000000 R15: 00007ffff1344990
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages