[moderation] [kernel?] general protection fault in srcu_gp_start_if_needed (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1e7857b28020 x86: don't re-generate cpufeaturemasks.h so e..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c3dc74580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4253e469c0d32ef6
dashboard link: https://syzkaller.appspot.com/bug?extid=cc9f5ca6b9758792a852
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/d0cdb19cb6e5/disk-1e7857b2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/50ca3bcf0fb8/vmlinux-1e7857b2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c532a7170308/bzImage-1e7857b2.xz

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

Oops: general protection fault, probably for non-canonical address 0xfc101bfff1100af1: 0000 [#1] SMP KASAN PTI
KASAN: maybe wild-memory-access in range [0xe080ffff88805788-0xe080ffff8880578f]
CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0-syzkaller-11144-g1e7857b28020 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
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+0xb2/0x12a0 kernel/rcu/srcutree.c:1263
Code: 42 c7 44 21 0d f3 f3 48 89 8c 24 90 00 00 00 42 c6 44 21 0f f3 48 89 7c 24 40 4c 8d 7f 38 4c 89 f8 48 c1 e8 03 48 89 44 24 28 <42> 80 3c 20 00 74 08 4c 89 ff e8 bf bd 81 00 bb 88 01 00 00 49 03
RSP: 0018:ffffc900000e7880 EFLAGS: 00010a02
RAX: 1c101ffff1100af1 RBX: 1ffffd1ffffada7a RCX: 1ffff9200001cf24
RDX: 0000000000000001 RSI: ffffe8ffffd6d3c8 RDI: e080ffff88805750
RBP: ffffc900000e79f0 R08: ffffffff905e2977 R09: 1ffffffff20bc52e
R10: dffffc0000000000 R11: fffffbfff20bc52f R12: dffffc0000000000
R13: ffffe8ffffd6d3c8 R14: ffffe8ffffd6d3c8 R15: e080ffff88805788
FS: 0000000000000000(0000) GS:ffff888124fe4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f54471ff000 CR3: 000000000eb38000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
srcu_invoke_callbacks+0x23a/0x4a0 kernel/rcu/srcutree.c:1805
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xac3/0x18e0 kernel/workqueue.c:3319
worker_thread+0x870/0xd50 kernel/workqueue.c:3400
kthread+0x7b7/0x940 kernel/kthread.c:464
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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+0xb2/0x12a0 kernel/rcu/srcutree.c:1263
Code: 42 c7 44 21 0d f3 f3 48 89 8c 24 90 00 00 00 42 c6 44 21 0f f3 48 89 7c 24 40 4c 8d 7f 38 4c 89 f8 48 c1 e8 03 48 89 44 24 28 <42> 80 3c 20 00 74 08 4c 89 ff e8 bf bd 81 00 bb 88 01 00 00 49 03
RSP: 0018:ffffc900000e7880 EFLAGS: 00010a02

RAX: 1c101ffff1100af1 RBX: 1ffffd1ffffada7a RCX: 1ffff9200001cf24
RDX: 0000000000000001 RSI: ffffe8ffffd6d3c8 RDI: e080ffff88805750
RBP: ffffc900000e79f0 R08: ffffffff905e2977 R09: 1ffffffff20bc52e
R10: dffffc0000000000 R11: fffffbfff20bc52f R12: dffffc0000000000
R13: ffffe8ffffd6d3c8 R14: ffffe8ffffd6d3c8 R15: e080ffff88805788
FS: 0000000000000000(0000) GS:ffff888124fe4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f54471ff000 CR3: 000000000eb38000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 42 c7 44 21 0d f3 f3 movl $0x8948f3f3,0xd(%rcx,%r12,1)
7: 48 89
9: 8c 24 90 mov %fs,(%rax,%rdx,4)
c: 00 00 add %al,(%rax)
e: 00 42 c6 add %al,-0x3a(%rdx)
11: 44 21 0f and %r9d,(%rdi)
14: f3 48 89 7c 24 40 xrelease mov %rdi,0x40(%rsp)
1a: 4c 8d 7f 38 lea 0x38(%rdi),%r15
1e: 4c 89 f8 mov %r15,%rax
21: 48 c1 e8 03 shr $0x3,%rax
25: 48 89 44 24 28 mov %rax,0x28(%rsp)
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 ff mov %r15,%rdi
34: e8 bf bd 81 00 call 0x81bdf8
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.