linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+19396db90a543f153fad@syzkaller.appspotmail.com>
To: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	 linux-next@vger.kernel.org, m.szyprowski@samsung.com,
	robin.murphy@arm.com,  sfr@canb.auug.org.au,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] linux-next build error (21)
Date: Wed, 23 Apr 2025 04:33:30 -0700	[thread overview]
Message-ID: <6808d00a.050a0220.7184a.0010.GAE@google.com> (raw)

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

                 reply	other threads:[~2025-04-23 11:33 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=6808d00a.050a0220.7184a.0010.GAE@google.com \
    --to=syzbot+19396db90a543f153fad@syzkaller.appspotmail.com \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robin.murphy@arm.com \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).