From: syzbot <syzbot+dfe85a6b612e19d45a07@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: [syzbot] [kernel?] general protection fault in srcu_invoke_callbacks
Date: Tue, 21 May 2024 02:11:33 -0700 [thread overview]
Message-ID: <000000000000435c360618f334d0@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: eb6a9339efeb Merge tag 'mm-nonmm-stable-2024-05-19-11-56' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1276c97c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2ea586e11acd6ec
dashboard link: https://syzkaller.appspot.com/bug?extid=dfe85a6b612e19d45a07
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-eb6a9339.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21782c1528d1/vmlinux-eb6a9339.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6c377678e8b1/bzImage-eb6a9339.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dfe85a6b612e19d45a07@syzkaller.appspotmail.com
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000030: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000180-0x0000000000000187]
CPU: 0 PID: 5282 Comm: kworker/0:4 Not tainted 6.9.0-syzkaller-09699-geb6a9339efeb #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:rcu_seq_current kernel/rcu/rcu.h:138 [inline]
RIP: 0010:srcu_invoke_callbacks+0x158/0x490 kernel/rcu/srcutree.c:1732
Code: 48 c1 ea 03 80 3c 02 00 0f 85 02 03 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5b 38 48 8d bb 80 01 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 d2 02 00 00 48 8b b3 80 01 00 00 48 8d 85 20 ff
RSP: 0018:ffffc90003c17bf8 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff816d1bfd
RDX: 0000000000000030 RSI: 0000000000000004 RDI: 0000000000000180
RBP: ffffe8ffad054220 R08: 0000000000000001 R09: fffff52000782f71
R10: 0000000000000003 R11: 0000000000000002 R12: 1ffff92000782f83
R13: ffffe8ffad054140 R14: ffffc90003c17c38 R15: ffffc90003c17d80
FS: 0000000000000000(0000) GS:ffff88802c000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc3fbc5ffc9 CR3: 0000000053e80000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work+0x958/0x1ad0 kernel/workqueue.c:3231
process_scheduled_works kernel/workqueue.c:3312 [inline]
worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393
kthread+0x2c1/0x3a0 kernel/kthread.c:389
ret_from_fork+0x45/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:rcu_seq_current kernel/rcu/rcu.h:138 [inline]
RIP: 0010:srcu_invoke_callbacks+0x158/0x490 kernel/rcu/srcutree.c:1732
Code: 48 c1 ea 03 80 3c 02 00 0f 85 02 03 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5b 38 48 8d bb 80 01 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 d2 02 00 00 48 8b b3 80 01 00 00 48 8d 85 20 ff
RSP: 0018:ffffc90003c17bf8 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff816d1bfd
RDX: 0000000000000030 RSI: 0000000000000004 RDI: 0000000000000180
RBP: ffffe8ffad054220 R08: 0000000000000001 R09: fffff52000782f71
R10: 0000000000000003 R11: 0000000000000002 R12: 1ffff92000782f83
R13: ffffe8ffad054140 R14: ffffc90003c17c38 R15: ffffc90003c17d80
FS: 0000000000000000(0000) GS:ffff88802c000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc3fbc5ffc9 CR3: 0000000053e80000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 48 c1 ea 03 shr $0x3,%rdx
4: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
8: 0f 85 02 03 00 00 jne 0x310
e: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
15: fc ff df
18: 48 8b 5b 38 mov 0x38(%rbx),%rbx
1c: 48 8d bb 80 01 00 00 lea 0x180(%rbx),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 d2 02 00 00 jne 0x306
34: 48 8b b3 80 01 00 00 mov 0x180(%rbx),%rsi
3b: 48 rex.W
3c: 8d .byte 0x8d
3d: 85 20 test %esp,(%rax)
3f: ff .byte 0xff
---
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 syzkaller@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
reply other threads:[~2024-05-21 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000435c360618f334d0@google.com \
--to=syzbot+dfe85a6b612e19d45a07@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.