[syzbot] linux-next build error (21)

5 views
Skip to first unread message

syzbot

unread,
Apr 23, 2025, 7:33:33 AM4/23/25
to io...@lists.linux.dev, linux-...@vger.kernel.org, linux...@vger.kernel.org, m.szyp...@samsung.com, robin....@arm.com, s...@canb.auug.org.au, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6ac908f24cd7 Add linux-next specific files for 20250423
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=160e9a6f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3bf8ea2b5f8ef14
dashboard link: https://syzkaller.appspot.com/bug?extid=19396db90a543f153fad
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6

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

kernel/dma/coherent.c:410:1: error: static assertion expression is not an integral constant expression
kernel/dma/contiguous.c:497:1: error: static assertion expression is not an integral constant expression
drivers/clk/clk-fixed-rate.c:197:1: error: static assertion expression is not an integral constant expression
drivers/clk/clk-fixed-factor.c:379:1: error: static assertion expression is not an integral constant expression

---
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

unread,
Jun 22, 2025, 8:33:16 PM6/22/25
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages