syzbot


WARNING in emulate_vsyscall

Status: upstream: reported C repro on 2024/04/06 00:40
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+adc0a92b543b3a46471b@syzkaller.appspotmail.com
First crash: 79d, last: 36d
Fix bisection: the issue occurs on the latest tested release (bisect log)
Crash: INFO: rcu detected stall in corrupted (log)
Repro: C syz .config
  
Bug presence (3)
Date Name Commit Repro Result
2024/06/05 linux-6.1.y (ToT) 88690811da69 C [report] INFO: rcu detected stall in corrupted
2024/04/21 upstream (ToT) ed30a4a51bb1 C [report] WARNING in emulate_vsyscall
2024/06/05 upstream (ToT) 2df0193e62cf C Didn't crash
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in emulate_vsyscall kernel C done done 3890 1002d 1183d 20/27 fixed on 2022/03/08 16:11
upstream WARNING in emulate_vsyscall (2) kernel C error 6 52d 82d 0/27 upstream: reported C repro on 2024/04/03 18:24
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/06/24 11:43 1h19m sebek.zoltek@gmail.com linux-6.1.y report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2024/06/22 09:16 8h05m fix candidate upstream job log (1)
2024/05/18 21:20 2h12m bisect fix linux-6.1.y job log (0) log

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5324 at arch/x86/entry/vsyscall/vsyscall_64.c:278 emulate_vsyscall+0xf3d/0x1240
Modules linked in:
CPU: 1 PID: 5324 Comm: syz-executor257 Not tainted 6.1.84-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:emulate_vsyscall+0xf3d/0x1240 arch/x86/entry/vsyscall/vsyscall_64.c:277
Code: 24 10 49 c7 c0 c0 51 e0 8a 4c 8b 4c 24 08 41 ff 36 41 54 55 41 55 53 e8 ca 90 87 09 48 83 c4 28 e9 8f fe ff ff e8 03 03 8a 00 <0f> 0b e9 83 fe ff ff 48 c7 c1 80 eb f9 8c 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90003eafe68 EFLAGS: 00010293
RAX: ffffffff810083ed RBX: 0000000000000100 RCX: ffff8880676b3b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff810081df R09: fffffbfff1ce6d46
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100ced6a8a
R13: ffffc90003eaff58 R14: 0000000000000000 R15: 1ffff920007d5ffe
FS:  00007f9b61f386c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000019 CR3: 0000000076bb7000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 do_user_addr_fault arch/x86/mm/fault.c:1337 [inline]
 handle_page_fault arch/x86/mm/fault.c:1462 [inline]
 exc_page_fault+0x154/0x660 arch/x86/mm/fault.c:1518
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:_end+0x6d3da000/0x0
Code: Unable to access opcode bytes at 0xffffffffff5fffd6.
RSP: 002b:00007f9b61f37bb8 EFLAGS: 00010246
RAX: ffffffffffffffda RBX: 0000000000000040 RCX: 00007f9b62788b59
RDX: 00007f9b61f37bc0 RSI: 00007f9b61f37cf0 RDI: 0000000000000019
RBP: 0400000000000000 R08: 00007f9b61f386c0 R09: 0000000000000000
R10: 0000000000000007 R11: 0000000000000246 R12: 00007f9b628131ec
R13: 0000000000000016 R14: 00007fffc77a4c10 R15: 00007fffc77a4cf8
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/06 01:21 linux-6.1.y 347385861c50 77230c29 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan WARNING in emulate_vsyscall
2024/04/13 06:10 linux-6.1.y bf1e3b1cb1e0 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan WARNING in emulate_vsyscall
2024/04/06 00:39 linux-6.1.y 347385861c50 77230c29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan WARNING in emulate_vsyscall
* Struck through repros no longer work on HEAD.