linux-kernel - [syzbot] linux-next build error (21)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <6808d00a.050a0220.7184a.0010.GAE@google.com>
Date: Wed, 23 Apr 2025 04:33:30 -0700
From: syzbot <syzbot+19396db90a543f153fad@...kaller.appspotmail.com>
To: iommu@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	linux-next@...r.kernel.org, m.szyprowski@...sung.com, robin.murphy@....com, 
	sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] linux-next build error (21)

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+19396db90a543f153fad@...kaller.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 syzkaller@...glegroups.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