[moderation] [kernel?] general protection fault in hash_net4_gc_do

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 99bd3cb0d12e Merge tag 'bcachefs-2024-02-05' of https://ev..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11f67e8fe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=53985487b59d9442
dashboard link: https://syzkaller.appspot.com/bug?extid=34ba8c67687fbf0b88f7
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [b...@alien8.de dave....@linux.intel.com h...@zytor.com linux-...@vger.kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/41c2f243f47c/disk-99bd3cb0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bdb1a0fc125d/vmlinux-99bd3cb0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f4080aef930c/bzImage-99bd3cb0.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]
CPU: 0 PID: 31539 Comm: kworker/0:1 Not tainted 6.8.0-rc3-syzkaller-00005-g99bd3cb0d12e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: events_power_efficient hash_net4_gc
RIP: 0010:__lock_acquire+0xe5b/0x3b40 kernel/locking/lockdep.c:5005
Code: 11 00 00 39 05 66 63 d6 11 0f 82 c7 05 00 00 ba 01 00 00 00 e9 e4 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 ea 48 c1 ea 03 <80> 3c 02 00 0f 85 30 1f 00 00 49 81 7d 00 e0 da 97 92 0f 84 7c f2
RSP: 0018:ffffc9000534f928 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000003 RSI: ffff88802ebe9dc0 RDI: 0000000000000018
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: ffffffff8f9d49d7 R11: ffffffff93421cf8 R12: 0000000000000000
R13: 0000000000000018 R14: 0000000000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30753000 CR3: 000000000d57a000 CR4: 00000000003506f0
Call Trace:
<TASK>
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
_raw_spin_lock_bh+0x33/0x40 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:356 [inline]
hash_net4_gc_do+0x116/0xb90 net/netfilter/ipset/ip_set_hash_gen.h:495
hash_net4_gc+0x260/0x470 net/netfilter/ipset/ip_set_hash_gen.h:583
process_one_work+0x889/0x15e0 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x8b9/0x12a0 kernel/workqueue.c:2787
kthread+0x2c6/0x3b0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__lock_acquire+0xe5b/0x3b40 kernel/locking/lockdep.c:5005
Code: 11 00 00 39 05 66 63 d6 11 0f 82 c7 05 00 00 ba 01 00 00 00 e9 e4 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 ea 48 c1 ea 03 <80> 3c 02 00 0f 85 30 1f 00 00 49 81 7d 00 e0 da 97 92 0f 84 7c f2
RSP: 0018:ffffc9000534f928 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000003 RSI: ffff88802ebe9dc0 RDI: 0000000000000018
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: ffffffff8f9d49d7 R11: ffffffff93421cf8 R12: 0000000000000000
R13: 0000000000000018 R14: 0000000000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30753000 CR3: 000000000d57a000 CR4: 00000000003506f0
----------------
Code disassembly (best guess):
0: 11 00 adc %eax,(%rax)
2: 00 39 add %bh,(%rcx)
4: 05 66 63 d6 11 add $0x11d66366,%eax
9: 0f 82 c7 05 00 00 jb 0x5d6
f: ba 01 00 00 00 mov $0x1,%edx
14: e9 e4 00 00 00 jmp 0xfd
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 4c 89 ea mov %r13,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 30 1f 00 00 jne 0x1f64
34: 49 81 7d 00 e0 da 97 cmpq $0xffffffff9297dae0,0x0(%r13)
3b: 92
3c: 0f .byte 0xf
3d: 84 .byte 0x84
3e: 7c f2 jl 0x32


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup