WARNING in jbd2_journal_destroy

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 41f36d7859a7 Linux 4.14.296
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f574a6880000
kernel config: https://syzkaller.appspot.com/x/.config?x=20cc5ea0fe276fa6
dashboard link: https://syzkaller.appspot.com/bug?extid=8774d1a45bd4713b7b25
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13a523ca880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=140d5eb6880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/941b591cedec/disk-41f36d78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2eea2720f8fc/vmlinux-41f36d78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7c3ce0be6b9a/bzImage-41f36d78.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ea9181bff901/mount_0.gz

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

should_failslab+0xd6/0x130 mm/failslab.c:32
slab_pre_alloc_hook mm/slab.h:421 [inline]
slab_alloc mm/slab.c:3376 [inline]
kmem_cache_alloc+0x40/0x3c0 mm/slab.c:3550
name 'info'
mempool_alloc+0x10e/0x2d0 mm/mempool.c:330
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7983 at fs/proc/generic.c:561 remove_proc_entry.cold+0x20/0x83 fs/proc/generic.c:561
bio_alloc_bioset+0x41b/0x830 block/bio.c:486
Kernel panic - not syncing: panic_on_warn set ...

bio_alloc include/linux/bio.h:422 [inline]
submit_bh_wbc+0xf5/0x6f0 fs/buffer.c:3121
submit_bh fs/buffer.c:3153 [inline]
ll_rw_block+0x151/0x190 fs/buffer.c:3203
__breadahead_gfp+0xac/0x150 fs/buffer.c:1406
sb_breadahead_unmovable include/linux/buffer_head.h:361 [inline]
__ext4_get_inode_loc+0xac8/0xf80 fs/ext4/inode.c:4661
__ext4_iget+0x25c/0x38e0 fs/ext4/inode.c:4799
ext4_get_journal_inode+0x2b/0x160 fs/ext4/super.c:4634
ext4_get_journal fs/ext4/super.c:4665 [inline]
ext4_load_journal fs/ext4/super.c:4825 [inline]
ext4_fill_super+0x91fc/0xb3c0 fs/ext4/super.c:4222
mount_bdev+0x2b3/0x360 fs/super.c:1134
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+0x46/0xbb
RIP: 0033:0x7f364b6874fa
RSP: 002b:00007fff5e7a4358 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f364b6874fa
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 00007fff5e7a4370
RBP: 00007fff5e7a4370 R08: 00007fff5e7a43b0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000005
R13: 00007fff5e7a43b0 R14: 0000000000000014 R15: 00000000200003e0
CPU: 1 PID: 7983 Comm: syz-executor235 Not tainted 4.14.296-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/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:964
RIP: 0010:remove_proc_entry.cold+0x20/0x83 fs/proc/generic.c:561
RSP: 0018:ffff88809d057938 EFLAGS: 00010286
RAX: 000000000000000b RBX: 1ffff11013a0af27 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bc9e0 RDI: ffffed1013a0af1d
RBP: 0000000000000000 R08: 000000000000000b R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff8799e8e0
R13: dffffc0000000000 R14: ffff88809c25e968 R15: ffff88809c25e950
jbd2_stats_proc_exit fs/jbd2/journal.c:1105 [inline]
jbd2_journal_destroy+0x41f/0x740 fs/jbd2/journal.c:1775
ext4_load_journal fs/ext4/super.c:4851 [inline]
ext4_fill_super+0x9340/0xb3c0 fs/ext4/super.c:4222
mount_bdev+0x2b3/0x360 fs/super.c:1134
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+0x46/0xbb
RIP: 0033:0x7f364b6874fa
RSP: 002b:00007fff5e7a4358 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f364b6874fa
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 00007fff5e7a4370
RBP: 00007fff5e7a4370 R08: 00007fff5e7a43b0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000005
R13: 00007fff5e7a43b0 R14: 0000000000000014 R15: 00000000200003e0
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