This seems like a Clang bug, right? The test for _Nullable is reversed or something?
regards, dan carpenter 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 <[email protected]> > > ## 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
