WARNING in sysfs_create_dir_ns (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 66722c42ec91 Linux 4.14.256
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11a5d791b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8004ce84f364d9
dashboard link: https://syzkaller.appspot.com/bug?extid=32d355dc81c40e6081ae
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+32d355...@syzkaller.appspotmail.com

do_xmote+0x453/0x580 fs/gfs2/glock.c:590
run_queue+0x1d3/0x4d0 fs/gfs2/glock.c:655
gfs2_glock_nq+0x830/0x1120 fs/gfs2/glock.c:1114
gfs2_glock_nq_init fs/gfs2/glock.h:228 [inline]
gfs2_permission+0x1cd/0x320 fs/gfs2/inode.c:1809
------------[ cut here ]------------
WARNING: CPU: 1 PID: 13606 at fs/sysfs/dir.c:30 sysfs_warn_dup.cold+0x17/0x26 fs/sysfs/dir.c:30
Kernel panic - not syncing: panic_on_warn set ...

do_inode_permission fs/namei.c:384 [inline]
__inode_permission+0x1f1/0x2f0 fs/namei.c:426
inode_permission+0x23/0xf0 fs/namei.c:476
may_open+0x1ab/0x2e0 fs/namei.c:2975
do_last fs/namei.c:3424 [inline]
path_openat+0x5bf/0x2970 fs/namei.c:3569
do_filp_open+0x179/0x3c0 fs/namei.c:3603
do_sys_open+0x296/0x410 fs/open.c:1081
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f0963aafa04
RSP: 002b:00007f0962a71f30 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f0963aafa04
RDX: 0000000000010000 RSI: 0000000020000100 RDI: 00000000ffffff9c
RBP: 0000000020000100 R08: 0000000000000000 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000010000
R13: 0000000020000100 R14: 00007f0962a72000 R15: 0000000020047a20
CPU: 1 PID: 13606 Comm: syz-executor.1 Not tainted 4.14.256-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
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:sysfs_warn_dup.cold+0x17/0x26 fs/sysfs/dir.c:30
RSP: 0018:ffff888099def728 EFLAGS: 00010282
RAX: 000000000000003a RBX: ffff888062d39790 RCX: 0000000000000000
RDX: 0000000000028460 RSI: ffffffff81442bf0 RDI: ffffed10133bdedb
RBP: ffff888095eac280 R08: 000000000000003a R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888238f76e00
R13: ffff8880b4001780 R14: ffff888062d39798 R15: ffff888063240ad8
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/0x2a10 fs/namespace.c:2902
SYSC_mount fs/namespace.c:3118 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3095
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fc88f49301a
RSP: 002b:00007fc88e406fa8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fc88f49301a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fc88e407000
RBP: 00007fc88e407040 R08: 00007fc88e407040 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fc88e407000 R15: 0000000020047a20
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.