From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Netdev <netdev@vger.kernel.org>,
clang-built-linux <llvm@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org
Cc: "David S. Miller" <davem@davemloft.net>,
Nathan Chancellor <nathan@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Eric Dumazet <edumazet@google.com>
Subject: net/sunrpc/sched.c: error: result of comparison against a string literal is unspecified (use an explicit string comparison function instead)
Date: Mon, 18 Mar 2024 14:55:54 +0530 [thread overview]
Message-ID: <CA+G9fYs=OTKAZS6g1P1Ewadfr0qoe6LgOVSohqkXmFXotEODdg@mail.gmail.com> (raw)
The following build warnings / errors noticed on x86 kselftests build with
clang nightly / clang-17 on Linux next tag next-20240318.
This build config is generated from kselftest merge configs [1].
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build log:
-----------
In file included from net/sunrpc/sched.c:31:
In file included from include/trace/events/sunrpc.h:2524:
In file included from include/trace/define_trace.h:102:
In file included from include/trace/trace_events.h:419:
include/trace/events/sunrpc.h:707:4: error: result of comparison
against a string literal is unspecified (use an explicit string
comparison function instead) [-Werror,-Wstring-compare]
667 | __assign_str(progname,
| ~~~~~~~~~~~~~~~~~~~~~~
668 | task->tk_client->cl_program->name);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
669 | __entry->version = task->tk_client->cl_vers;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
670 | __assign_str(procedure,
task->tk_msg.rpc_proc->p_name);
|
[1] steps to reproduce:
-----------
tuxmake --runtime podman --target-arch x86_64 --toolchain
clang-nightly --kconfig
https://storage.tuxsuite.com/public/linaro/lkft/builds/2dqIWv3Qq5qYmJfnmKfkSg9fvN0/config
LLVM=1 LLVM_IAS=1 debugkernel cpupower headers kernel kselftest
modules
Links:
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2dqIWv3Qq5qYmJfnmKfkSg9fvN0/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240318/testrun/23069554/suite/build/test/clang-nightly-lkftconfig-kselftest/log
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240318/testrun/23069554/suite/build/test/clang-nightly-lkftconfig-kselftest/details/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-03-18 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:25 Naresh Kamboju [this message]
2024-03-18 15:43 ` net/sunrpc/sched.c: error: result of comparison against a string literal is unspecified (use an explicit string comparison function instead) Nathan Chancellor
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='CA+G9fYs=OTKAZS6g1P1Ewadfr0qoe6LgOVSohqkXmFXotEODdg@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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).