WARNING in gfs2_lm_withdraw

[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=15b336ca880000
kernel config: https://syzkaller.appspot.com/x/.config?x=20cc5ea0fe276fa6
dashboard link: https://syzkaller.appspot.com/bug?extid=ed172c61c7d54f4db429
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/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

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

inode = 3 2074
function = gfs2_dirent_scan, file = fs/gfs2/dir.c, line = 607
sysfs: cannot create duplicate filename '/fs/gfs2/syz:syz'
gfs2: fsid=syz:syz.0: about to withdraw this file system
------------[ cut here ]------------
WARNING: CPU: 1 PID: 13106 at fs/sysfs/dir.c:30 sysfs_warn_dup.cold+0x17/0x26 fs/sysfs/dir.c:30
gfs2: fsid=syz:syz.0: withdrawn
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 13087 Comm: syz-executor.5 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
gfs2_lm_withdraw.cold+0x1d8/0x251 fs/gfs2/util.c:73
gfs2_consist_inode_i+0xca/0x110 fs/gfs2/util.c:161
gfs2_dirent_scan+0x1b3/0x200 fs/gfs2/dir.c:607
gfs2_dirent_search+0x398/0x490 fs/gfs2/dir.c:856
gfs2_dir_check+0x70/0x290 fs/gfs2/dir.c:1685
gfs2_jindex_hold fs/gfs2/ops_fstype.c:575 [inline]
init_journal fs/gfs2/ops_fstype.c:679 [inline]
init_inodes+0x38a/0x18d0 fs/gfs2/ops_fstype.c:802
fill_super+0x1721/0x2310 fs/gfs2/ops_fstype.c:1172
gfs2_mount+0x439/0x510 fs/gfs2/ops_fstype.c:1335
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:0x7fc0450fdada
RSP: 002b:00007fc04366ef88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fc0450fdada
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fc04366efe0
RBP: 00007fc04366f020 R08: 00007fc04366f020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fc04366efe0 R15: 0000000020000040
CPU: 1 PID: 13106 Comm: syz-executor.2 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
gfs2: fsid=syz:syz.0: can't read journal index: -5
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:sysfs_warn_dup.cold+0x17/0x26 fs/sysfs/dir.c:30
RSP: 0018:ffff88805292f728 EFLAGS: 00010282
RAX: 000000000000003a RBX: ffff888046538110 RCX: 0000000000000000
RDX: 0000000000012fde RSI: ffffffff81443130 RDI: ffffed100a525edb
RBP: ffff8880984c6cc0 R08: 000000000000003a R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888238fc18c0
R13: ffff8880abfdd8c0 R14: ffff888046538118 R15: ffff8880a8e98058
sysfs_create_dir_ns+0x16f/0x1d0 fs/sysfs/dir.c:59
create_dir lib/kobject.c:71 [inline]
kobject_add_internal+0x28b/0x930 lib/kobject.c:229
kobject_add_varg lib/kobject.c:364 [inline]
kobject_init_and_add+0xde/0x120 lib/kobject.c:436
gfs2_sys_fs_add+0x184/0x3f0 fs/gfs2/sys.c:652
fill_super+0x118b/0x2310 fs/gfs2/ops_fstype.c:1122
gfs2_mount+0x439/0x510 fs/gfs2/ops_fstype.c:1335
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:0x7f6d3a8b8ada
RSP: 002b:00007f6d38e29f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f6d3a8b8ada
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f6d38e29fe0
RBP: 00007f6d38e2a020 R08: 00007f6d38e2a020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f6d38e29fe0 R15: 0000000020000040
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.