syzbot


riscv/for-next build error

Status: upstream: reported on 2025/09/19 14:42
Reported-by: syzbot+8ea9d12facf13c334f88@syzkaller.appspotmail.com
First crash: 2h47m, last: 2h47m
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] riscv/for-next build error 0 (1) 2025/09/19 14:42

Sample crash report:
arch/riscv/kernel/entry.S:78: Error: unrecognized opcode `alternative("sfence.vma", "nop",0,86,1)'
arch/riscv/kernel/entry.S:446: Error: unrecognized opcode `alternative(".dword do_trap_insn_fault", ".dword sifive_cip_453_insn_fault_trp",0x489,0,1)'
arch/riscv/kernel/entry.S:458: Error: unrecognized opcode `alternative(".dword do_page_fault", ".dword sifive_cip_453_page_fault_trp",0x489,0,1)'

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/19 14:01 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next a054965b36af 67c37560 .config console log report ci-qemu2-riscv64 riscv/for-next build error
* Struck through repros no longer work on HEAD.