From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Cc: KernelCI bot <bot@kernelci.org>,
kernelci@lists.linux.dev, kernelci-results@groups.io,
regressions@lists.linux.dev, gus@collabora.com,
linux-next@vger.kernel.org, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [REGRESSION] next/pending-fixes: (build) error: unknown warning option '-Wno-suggest-attribute=format'; did...
Date: Tue, 16 Dec 2025 12:25:14 +1100 [thread overview]
Message-ID: <20251216122514.7ee70d5f@canb.auug.org.au> (raw)
In-Reply-To: <176584314280.2550.10885082269394184097@77bfb67944a2>
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
Hi all,
On Mon, 15 Dec 2025 23:59:03 -0000 KernelCI bot <bot@kernelci.org> wrote:
>
> Hello,
>
> New build issue found on next/pending-fixes:
>
> ---
> error: unknown warning option '-Wno-suggest-attribute=format'; did you mean '-Wno-property-attribute-mismatch'? [-Werror,-Wunknown-warning-option] in kernel/bpf/helpers.o (scripts/Makefile.build:287) [logspec:kbuild,kbuild.compiler.error]
> ---
>
> - dashboard: https://d.kernelci.org/i/maestro:32e32983183c2c586f588a4a3a7cda83311d5be9
> - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> - commit HEAD: 326785a1dd4cea4065390fb99b0249781c9912bf
>
>
> Please include the KernelCI tag when submitting a fix:
>
> Reported-by: kernelci.org bot <bot@kernelci.org>
>
>
> Log excerpt:
> =====================================================
> CC kernel/bpf/helpers.o
> error: unknown warning option '-Wno-suggest-attribute=format'; did you mean '-Wno-property-attribute-mismatch'? [-Werror,-Wunknown-warning-option]
>
> =====================================================
>
>
> # Builds where the incident occurred:
>
> ## defconfig on (arm64):
> - compiler: clang-21
> - config: https://files.kernelci.org/kbuild-clang-21-arm64-mainline-694097d2cbfd84c3cdba292d/.config
> - dashboard: https://d.kernelci.org/build/maestro:694097d2cbfd84c3cdba292d
>
>
> #kernelci issue maestro:32e32983183c2c586f588a4a3a7cda83311d5be9
>
> --
> This is an experimental report format. Please send feedback in!
> Talk to us at kernelci@lists.linux.dev
>
> Made with love by the KernelCI team - https://kernelci.org
>
Presumably caused by commit
ba34388912b5 ("bpf: Disable false positive -Wsuggest-attribute=format warning")
in the bpf tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2025-12-16 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176584314280.2550.10885082269394184097@77bfb67944a2>
2025-12-16 1:25 ` Stephen Rothwell [this message]
2025-12-16 1:31 ` [REGRESSION] next/pending-fixes: (build) error: unknown warning option '-Wno-suggest-attribute=format'; did Ihor Solodrai
2025-12-16 1:37 ` Alexei Starovoitov
2025-12-16 1:42 ` Alexei Starovoitov
2025-12-16 2:07 ` Ihor Solodrai
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=20251216122514.7ee70d5f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ast@kernel.org \
--cc=bot@kernelci.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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