From: Nathan Chancellor <nathan@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
clang-built-linux <llvm@lists.linux.dev>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Sasha Levin <sashal@kernel.org>
Subject: Re: selftests/filesystem: clang warning null passed to a callee that requires a non-null argument [-Wnonnull]
Date: Wed, 11 Jun 2025 10:50:52 -0700 [thread overview]
Message-ID: <20250611175052.GA2307190@ax162> (raw)
In-Reply-To: <aEmzK5B4pbF5MZ6Y@stanley.mountain>
On Wed, Jun 11, 2025 at 07:47:39PM +0300, Dan Carpenter wrote:
> This seems like a Clang bug, right? The test for _Nullable is reversed
> or something?
My copy of unistd.h has
/* Execute program relative to a directory file descriptor. */
extern int execveat (int __fd, const char *__path, char *const __argv[],
char *const __envp[], int __flags)
__THROW __nonnull ((2, 3));
so I think the warning is valid in this case. I will note that
tools/testing/selftests/exec/recursion-depth.c uses execve() with a NULL
argv and disables -Wnonnull so maybe that should happen for this test
case too? Or should that NULL be changed into a ""?
> On Thu, Jun 05, 2025 at 05:41:01PM +0530, Naresh Kamboju wrote:
> > Regressions found on arm, arm64 and x86_64 building warnings with clang-20
> > and clang-nightly started from Linux next-20250603
> >
> > Regressions found on arm, arm64 and x86_64
> > - selftests/filesystem
> >
> > Regression Analysis:
> > - New regression? Yes
> > - Reproducible? Yes
> >
> > First seen on the next-20250603
> > Good: next-20250530
> > Bad: next-20250603
> >
> > Test regression: arm arm64 x86_64 clang warning null passed to a
> > callee that requires a non-null argument [-Wnonnull]
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > ## Build warnings
> > make[4]: Entering directory '/builds/linux/tools/testing/selftests/filesystems'
> > CC devpts_pts
> > CC file_stressor
> > CC anon_inode_test
> > anon_inode_test.c:45:37: warning: null passed to a callee that
> > requires a non-null argument [-Wnonnull]
> > 45 | ASSERT_LT(execveat(fd_context, "", NULL, NULL,
> > AT_EMPTY_PATH), 0);
> > | ^~~~
> >
> > ## Source
> > * Kernel version: 6.15.0-next-20250605
> > * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> > * Git sha: a0bea9e39035edc56a994630e6048c8a191a99d8
> > * Toolchain: Debian clang version 21.0.0
> > (++20250529012636+c474f8f2404d-1~exp1~20250529132821.1479)
> >
> > ## Build
> > * Test log: https://qa-reports.linaro.org/api/testruns/28651387/log_file/
> > * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2xzM4wMl8SvuLKE3mw3csiuv3Jz/
> > * Kernel config:
> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2xzM4wMl8SvuLKE3mw3csiuv3Jz/config
> >
> > --
> > Linaro LKFT
> > https://lkft.linaro.org
next prev parent reply other threads:[~2025-06-11 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 12:11 selftests/filesystem: clang warning null passed to a callee that requires a non-null argument [-Wnonnull] Naresh Kamboju
2025-06-11 16:47 ` Dan Carpenter
2025-06-11 17:50 ` Nathan Chancellor [this message]
2025-06-11 18:29 ` Dan Carpenter
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=20250611175052.GA2307190@ax162 \
--to=nathan@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.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 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).