From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: mainline build failure due to 281d0c962752 ("fortify: Add Clang support")
Date: Wed, 22 Jun 2022 11:23:34 +0100 [thread overview]
Message-ID: <YrLtpixBqWDmZT/V@debian> (raw)
Hi All,
I have recently (since yesterday) started building the mainline kernel
with clang-14 and I am seeing a build failure with allmodconfig.
In file included from drivers/net/ethernet/huawei/hinic/hinic_devlink.c:15:
In file included from ./include/linux/netlink.h:7:
In file included from ./include/linux/skbuff.h:15:
In file included from ./include/linux/time.h:60:
In file included from ./include/linux/time32.h:13:
In file included from ./include/linux/timex.h:67:
In file included from ./arch/x86/include/asm/timex.h:5:
In file included from ./arch/x86/include/asm/processor.h:22:
In file included from ./arch/x86/include/asm/msr.h:11:
In file included from ./arch/x86/include/asm/cpumask.h:5:
In file included from ./include/linux/cpumask.h:12:
In file included from ./include/linux/bitmap.h:11:
In file included from ./include/linux/string.h:253:
./include/linux/fortify-string.h:344:4: error: call to __write_overflow_field declared with 'warning' attribute: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror,-Wattribute-warning]
__write_overflow_field(p_size_field, size);
After a bisect it pointed to 281d0c962752 ("fortify: Add Clang support").
Since it was introduced in v5.18, not sure if its already reported before.
--
Regards
Sudip
next reply other threads:[~2022-06-22 10:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 10:23 Sudip Mukherjee [this message]
2022-06-22 13:47 ` mainline build failure due to 281d0c962752 ("fortify: Add Clang support") Linus Torvalds
2022-06-22 15:01 ` Nathan Chancellor
2022-06-22 16:21 ` Linus Torvalds
2022-06-22 17:26 ` Sudip Mukherjee
2022-06-22 17:48 ` Linus Torvalds
2022-06-22 22:40 ` Nick Desaulniers
2022-06-23 10:12 ` David Laight
2022-06-23 23:33 ` Nick Desaulniers
2022-06-28 22:42 ` Josh Poimboeuf
2022-06-29 16:08 ` Linus Torvalds
2022-06-29 16:34 ` Josh Poimboeuf
2022-06-29 21:21 ` Nick Desaulniers
2022-06-29 21:39 ` Linus Torvalds
2022-06-22 18:07 ` Jakub Kicinski
2022-06-22 15:08 ` Sudip Mukherjee
2022-06-22 15:19 ` Linus Torvalds
2022-06-22 16:00 ` Sudip Mukherjee
2022-06-22 16:07 ` Linus Torvalds
2022-06-22 16:16 ` Sudip Mukherjee
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=YrLtpixBqWDmZT/V@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.