netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Shuah Khan <shuah@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Elizabeth Figura <zfigura@codeweavers.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Eric Dumazet <edumazet@google.com>, Kees Cook <kees@kernel.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	wine-devel@winehq.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org, Kuniyuki Iwashima <kuniyu@google.com>
Subject: Re: [PATCH 06/13] selftest: af_unix: Support compilers without flex-array-member-not-at-end support
Date: Thu, 4 Dec 2025 09:40:54 -0800	[thread overview]
Message-ID: <20251204094054.01c15d1e@kernel.org> (raw)
In-Reply-To: <20251204161729.2448052-7-linux@roeck-us.net>

On Thu,  4 Dec 2025 08:17:20 -0800 Guenter Roeck wrote:
> -CFLAGS += $(KHDR_INCLUDES) -Wall -Wflex-array-member-not-at-end
> +CFLAGS += $(KHDR_INCLUDES) -Wall $(call cc-option,-Wflex-array-member-not-at-end)

Hm, the Claude code review we have hooked up to patchwork says:

  Is cc-option available in the selftest build environment? Looking at
  tools/testing/selftests/lib.mk (included at line 14), it doesn't include
  scripts/Makefile.compiler where cc-option is defined. When cc-option is
  undefined, $(call cc-option,...) expands to an empty string, which means
  the -Wflex-array-member-not-at-end flag won't be added even on compilers
  that support it.

  This defeats the purpose of commit 1838731f1072c which added the warning
  flag to catch flexible array issues.

  For comparison, tools/testing/selftests/nolibc/Makefile explicitly
  includes scripts/Makefile.compiler before using cc-option.

Testing it:

$ make -C tools/testing/selftests/ TARGETS=net/af_unix Q= V=1
make: Entering directory '/home/kicinski/devel/linux/tools/testing/selftests'
make[1]: Entering directory '/home/kicinski/devel/linux/tools/testing/selftests/net/af_unix'
gcc -isystem /home/kicinski/devel/linux/usr/include -Wall  -D_GNU_SOURCE=     diag_uid.c  -o /home/kicinski/devel/linux/tools/testing/selftests/net/af_unix/diag_uid

looks like the flag just disappears. Even tho:

gcc version 15.2.1 

  reply	other threads:[~2025-12-04 17:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 16:17 [PATCH 00/13] selftests: Fix problems seen when building with -Werror Guenter Roeck
2025-12-04 16:17 ` [PATCH 01/13] clone3: clone3_cap_checkpoint_restore: Fix build errors seen " Guenter Roeck
2025-12-04 16:17 ` [PATCH 02/13] selftests: ntsync: Fix build errors -seen " Guenter Roeck
2025-12-04 16:17 ` [PATCH 03/13] selftests/filesystems: fclog: Fix build errors seen " Guenter Roeck
2025-12-04 16:17 ` [PATCH 04/13] selftests/filesystems: file_stressor: Fix build error " Guenter Roeck
2025-12-04 16:17 ` [PATCH 05/13] selftests/filesystems: anon_inode_test: " Guenter Roeck
2025-12-04 16:17 ` [PATCH 06/13] selftest: af_unix: Support compilers without flex-array-member-not-at-end support Guenter Roeck
2025-12-04 17:40   ` Jakub Kicinski [this message]
2025-12-04 17:58     ` Guenter Roeck
2025-12-04 16:17 ` [PATCH 07/13] selftest/futex: Comment out test_futex_mpol Guenter Roeck
2025-12-04 16:17 ` [PATCH 08/13] selftests: net: netlink-dumps: Avoid uninitialized variable error Guenter Roeck
2025-12-04 16:17 ` [PATCH 09/13] selftests/seccomp: Fix build error seen with -Werror Guenter Roeck
2025-12-04 16:17 ` [PATCH 10/13] selftests: net: Work around " Guenter Roeck
2025-12-04 16:30   ` Jakub Kicinski
2025-12-04 17:21     ` Guenter Roeck
2025-12-04 16:17 ` [PATCH 11/13] selftests/fs/mount-notify: Fix build failure " Guenter Roeck
2025-12-04 16:17 ` [PATCH 12/13] selftests/fs/mount-notify-ns: Fix build failures " Guenter Roeck
2025-12-04 16:17 ` [PATCH 13/13] selftests: net: tfo: Fix build error " Guenter Roeck
2025-12-04 16:27 ` [PATCH 00/13] selftests: Fix problems seen when building " Jakub Kicinski
2025-12-04 17:16   ` Guenter Roeck
2025-12-04 17:43     ` Jakub Kicinski
2025-12-04 17:56       ` Guenter Roeck
2025-12-04 20:03     ` Kees Cook
2025-12-04 20:07       ` Guenter Roeck

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=20251204094054.01c15d1e@kernel.org \
    --to=kuba@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=edumazet@google.com \
    --cc=kees@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wine-devel@winehq.org \
    --cc=zfigura@codeweavers.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).