general protection fault in pwq_activate_delayed_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 179ef7fe8677 Linux 4.14.300
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=144a05d3880000
kernel config: https://syzkaller.appspot.com/x/.config?x=aa85f51ec321d5a9
dashboard link: https://syzkaller.appspot.com/bug?extid=0cd80ff6f5e350494428
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/d311ef57b59a/disk-179ef7fe.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/25bf5d729f69/vmlinux-179ef7fe.xz
kernel image: https://storage.googleapis.com/syzbot-assets/db9b96571e69/bzImage-179ef7fe.xz

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

gfs2: fsid=syz:syz.0: jid=0: Looking at journal...
gfs2: fsid=syz:syz.0: jid=0: Done
gfs2: fsid=syz:syz.0: first mount done, others may mount
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 10231 Comm: syz-executor.4 Not tainted 4.14.300-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff888051b9a180 task.stack: ffff888051428000
RIP: 0010:pwq_activate_delayed_work+0x95/0x3c0 kernel/workqueue.c:1120
RSP: 0018:ffff88805142fa60 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffffe8ffffd9a059 RCX: ffffc90006e7f000
RDX: 0000000000000000 RSI: ffffffff81358f64 RDI: 0000000000000086
RBP: 0000000000000001 R08: ffffffff8b9cb718 R09: 00000000000c0031
R10: ffff888051b9aa80 R11: ffff888051b9a180 R12: 0000000000000000
R13: fffff91ffffb340b R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f858d047700(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffebf8b8be8 CR3: 00000000974e5000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
pwq_activate_first_delayed kernel/workqueue.c:1132 [inline]
pwq_adjust_max_active+0x236/0x590 kernel/workqueue.c:3510
__alloc_workqueue_key+0x64e/0x1080 kernel/workqueue.c:4079
xfs_init_mount_workqueues+0x15e/0x6d0 fs/xfs/xfs_super.c:872
xfs_fs_fill_super+0x6a8/0x1380 fs/xfs/xfs_super.c:1595
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+0x5e/0xd3
Code: e8 71 c8 1f 00 89 ed 48 0f a3 2d 7f a8 d3 08 0f 82 9c 00 00 00 e8 5c c8 1f 00 4c 89 e2 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 e7 02 00 00 48 b8 00 00 00 00 00 fc ff df 4d
RIP: pwq_activate_delayed_work+0x95/0x3c0 kernel/workqueue.c:1120 RSP: ffff88805142fa60
---[ end trace 3842c496d6c883aa ]---
----------------
Code disassembly (best guess):
0: e8 71 c8 1f 00 callq 0x1fc876
5: 89 ed mov %ebp,%ebp
7: 48 0f a3 2d 7f a8 d3 bt %rbp,0x8d3a87f(%rip) # 0x8d3a88e
e: 08
f: 0f 82 9c 00 00 00 jb 0xb1
15: e8 5c c8 1f 00 callq 0x1fc876
1a: 4c 89 e2 mov %r12,%rdx
1d: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
24: fc ff df
27: 48 c1 ea 03 shr $0x3,%rdx
* 2b: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2f: 0f 85 e7 02 00 00 jne 0x31c
35: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
3c: fc ff df
3f: 4d rex.WRB


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