From: syzbot <syzbot+8ea9d12facf13c334f88@syzkaller.appspotmail.com>
To: alex@ghiti.fr, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, paul.walmsley@sifive.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] riscv/for-next build error
Date: Fri, 19 Sep 2025 07:42:32 -0700 [thread overview]
Message-ID: <68cd6bd8.a00a0220.37dadf.001b.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a054965b36af riscv: errata: Fix the PAUSE Opcode for MIPS ..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=150c1858580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a6ae75a6b3af4c52
dashboard link: https://syzkaller.appspot.com/bug?extid=8ea9d12facf13c334f88
compiler: riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: riscv64
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8ea9d12facf13c334f88@syzkaller.appspotmail.com
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)'
---
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2025-09-19 14:42 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=68cd6bd8.a00a0220.37dadf.001b.GAE@google.com \
--to=syzbot+8ea9d12facf13c334f88@syzkaller.appspotmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox