kernel BUG at fs/gfs2/glock.c:LINE!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 27ce4f2a Linux 4.14.206
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16ba9fdc500000
kernel config: https://syzkaller.appspot.com/x/.config?x=32258a0e1fac372d
dashboard link: https://syzkaller.appspot.com/bug?extid=99cc9642e32c39020043
compiler: gcc (GCC) 10.1.0-syz 20200507

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+99cc96...@syzkaller.appspotmail.com

gfs2: pid: 15071
gfs2: lock type: 8 req lock state : 1
gfs2: G: s:EX n:8/1 f:qb t:EX d:EX/0 a:0 v:0 r:5 m:20
gfs2: H: s:EX f:cH e:0 p:15071 [syz-executor.5] gfs2_glock_nq_init fs/gfs2/glock.h:226 [inline]
gfs2: H: s:EX f:cH e:0 p:15071 [syz-executor.5] do_sync+0x3f0/0xba0 fs/gfs2/quota.c:893
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:1082!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 15071 Comm: syz-executor.5 Not tainted 4.14.206-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff888051bec5c0 task.stack: ffff888055378000
RIP: 0010:add_to_queue fs/gfs2/glock.c:1082 [inline]
RIP: 0010:gfs2_glock_nq.cold+0x279/0x2dd fs/gfs2/glock.c:1107
RSP: 0018:ffff88805537fa88 EFLAGS: 00010296
RAX: ffffed100aa6ff32 RBX: ffff88809d01ed20 RCX: 1ffff1100a37d9dd
RDX: 0000000000000000 RSI: 0000000000000005 RDI: ffffffff87c09d70
RBP: 0000000000003adf R08: 0000000000000044 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880a2684638
R13: ffff88809d01ed20 R14: 0000000000000001 R15: 0000000000000000
FS: 00000000021e0940(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000021e9a98 CR3: 0000000054633000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
gfs2_glock_nq_init fs/gfs2/glock.h:228 [inline]
do_sync+0x3f8/0xba0 fs/gfs2/quota.c:893
gfs2_quota_sync+0x4f1/0x690 fs/gfs2/quota.c:1299
gfs2_sync_fs+0x40/0xa0 fs/gfs2/super.c:946
__sync_filesystem fs/sync.c:39 [inline]
sync_filesystem fs/sync.c:64 [inline]
sync_filesystem+0xe2/0x230 fs/sync.c:48
generic_shutdown_super+0x70/0x370 fs/super.c:432
kill_block_super+0x95/0xe0 fs/super.c:1161
gfs2_kill_sb+0x12c/0x1a0 fs/gfs2/ops_fstype.c:1409
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
deactivate_super+0x7f/0xa0 fs/super.c:350
cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4608e7
RSP: 002b:00007ffd6d5f3158 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000041f43 RCX: 00000000004608e7
RDX: 00000000004031f8 RSI: 0000000000000002 RDI: 00007ffd6d5f3200
RBP: 00000000000000a0 R08: 0000000000000000 R09: 000000000000000a
R10: 0000000000000005 R11: 0000000000000246 R12: 00007ffd6d5f4290
R13: 00000000021e1a60 R14: 0000000000000000 R15: 00007ffd6d5f4290
Code: c1 ea 03 0f b6 04 02 84 c0 74 04 3c 03 7e 6c 8b 73 18 44 89 f2 48 c7 c7 40 7b c0 87 e8 ff f0 84 fe 4c 89 ee 31 ff e8 44 92 ff ff <0f> 0b e8 2d 35 c0 fe 4c 8b 04 24 e9 ac fd ff ff 31 ed e9 14 fe
RIP: add_to_queue fs/gfs2/glock.c:1082 [inline] RSP: ffff88805537fa88
RIP: gfs2_glock_nq.cold+0x279/0x2dd fs/gfs2/glock.c:1107 RSP: ffff88805537fa88
---[ end trace 7ac206a0fc75e8ff ]---


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