]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
selftests/nolibc: avoid passing NULL to printf("%s")
authorThomas Weißschuh <linux@weissschuh.net>
Wed, 7 Aug 2024 21:51:44 +0000 (23:51 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 10 Oct 2024 10:03:21 +0000 (12:03 +0200)
[ Upstream commit f1a58f61d88642ae1e6e97e9d72d73bc70a93cb8 ]

Clang on higher optimization levels detects that NULL is passed to
printf("%s") and warns about it.
While printf() from nolibc gracefully handles that NULL,
it is undefined behavior as per POSIX, so the warning is reasonable.
Avoid the warning by transforming NULL into a non-NULL placeholder.

Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Acked-by: Willy Tarreau <w@1wt.eu>
Link: https://lore.kernel.org/r/20240807-nolibc-llvm-v2-8-c20f2f5fc7c2@weissschuh.net
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
tools/testing/selftests/nolibc/nolibc-test.c

index 093d0512f4c57aa338808516b8b760470f968550..8cbb51dca0cd6b8d5616f65bc16eef136e5531a4 100644 (file)
@@ -542,7 +542,7 @@ int expect_strzr(const char *expr, int llen)
 {
        int ret = 0;
 
-       llen += printf(" = <%s> ", expr);
+       llen += printf(" = <%s> ", expr ? expr : "(null)");
        if (expr) {
                ret = 1;
                result(llen, FAIL);
@@ -561,7 +561,7 @@ int expect_strnz(const char *expr, int llen)
 {
        int ret = 0;
 
-       llen += printf(" = <%s> ", expr);
+       llen += printf(" = <%s> ", expr ? expr : "(null)");
        if (!expr) {
                ret = 1;
                result(llen, FAIL);