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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7fa366f1b6e3 Add linux-next specific files for 20241218
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11df37e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=26a4b4cc7f877b28
dashboard link: https://syzkaller.appspot.com/bug?extid=04e1026bec82f28c80da
compiler: Debian clang version 15.0.6, 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/76406ccde331/disk-7fa366f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/49c56a285987/vmlinux-7fa366f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92d20cf0cd8a/bzImage-7fa366f1.xz

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

Oops: general protection fault, probably for non-canonical address 0xf61ffbf1100a460f: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: maybe wild-memory-access in range [0xb0ffff8880523078-0xb0ffff888052307f]
CPU: 0 UID: 0 PID: 973 Comm: kworker/0:2 Not tainted 6.13.0-rc3-next-20241218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:check_init_srcu_struct kernel/rcu/srcutree.c:410 [inline]
RIP: 0010:srcu_gp_start_if_needed+0xb0/0x11e0 kernel/rcu/srcutree.c:1258
Code: f2 f2 f2 00 66 42 c7 44 21 0d f3 f3 48 89 8c 24 90 00 00 00 42 c6 44 21 0f f3 4c 8d 6f 38 4c 89 e8 48 c1 e8 03 48 89 44 24 40 <42> 80 3c 20 00 74 08 4c 89 ef e8 d1 15 81 00 bb 88 01 00 00 49 03
RSP: 0018:ffffc90003f67880 EFLAGS: 00010a06
RAX: 161ffff1100a460f RBX: 1ffffd1ffff8cda5 RCX: 1ffff920007ecf24
RDX: 0000000000000001 RSI: ffffe8ffffc66d20 RDI: b0ffff8880523043
RBP: ffffc90003f679f0 R08: ffffffff942d1877 R09: 1ffffffff285a30e
R10: dffffc0000000000 R11: fffffbfff285a30f R12: dffffc0000000000
R13: b0ffff888052307b R14: b0ffff8880523043 R15: ffffffff81a4defc
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd464e269a2 CR3: 0000000029538000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
srcu_invoke_callbacks+0x237/0x490 kernel/rcu/srcutree.c:1795
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x7a9/0x920 kernel/kthread.c:464
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:check_init_srcu_struct kernel/rcu/srcutree.c:410 [inline]
RIP: 0010:srcu_gp_start_if_needed+0xb0/0x11e0 kernel/rcu/srcutree.c:1258
Code: f2 f2 f2 00 66 42 c7 44 21 0d f3 f3 48 89 8c 24 90 00 00 00 42 c6 44 21 0f f3 4c 8d 6f 38 4c 89 e8 48 c1 e8 03 48 89 44 24 40 <42> 80 3c 20 00 74 08 4c 89 ef e8 d1 15 81 00 bb 88 01 00 00 49 03
RSP: 0018:ffffc90003f67880 EFLAGS: 00010a06
RAX: 161ffff1100a460f RBX: 1ffffd1ffff8cda5 RCX: 1ffff920007ecf24
RDX: 0000000000000001 RSI: ffffe8ffffc66d20 RDI: b0ffff8880523043
RBP: ffffc90003f679f0 R08: ffffffff942d1877 R09: 1ffffffff285a30e
R10: dffffc0000000000 R11: fffffbfff285a30f R12: dffffc0000000000
R13: b0ffff888052307b R14: b0ffff8880523043 R15: ffffffff81a4defc
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd464e269a2 CR3: 0000000029538000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: f2 f2 f2 00 66 42 repnz repnz repnz add %ah,0x42(%rsi)
6: c7 44 21 0d f3 f3 48 movl $0x8948f3f3,0xd(%rcx,%riz,1)
d: 89
e: 8c 24 90 mov %fs,(%rax,%rdx,4)
11: 00 00 add %al,(%rax)
13: 00 42 c6 add %al,-0x3a(%rdx)
16: 44 21 0f and %r9d,(%rdi)
19: f3 4c 8d 6f 38 repz lea 0x38(%rdi),%r13
1e: 4c 89 e8 mov %r13,%rax
21: 48 c1 e8 03 shr $0x3,%rax
25: 48 89 44 24 40 mov %rax,0x40(%rsp)
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 ef mov %r13,%rdi
34: e8 d1 15 81 00 call 0x81160a
39: bb 88 01 00 00 mov $0x188,%ebx
3e: 49 rex.WB
3f: 03 .byte 0x3


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.