From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: pointer_masking.c:216:25: warning: format string is not a string literal (potentially insecure)
Date: Sun, 26 Oct 2025 03:16:52 +0800 [thread overview]
Message-ID: <202510260342.qQLArXOY-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Charlie Jenkins <charlie@rivosinc.com>
CC: Palmer Dabbelt <palmer@rivosinc.com>
CC: Andrew Jones <ajones@ventanamicro.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9bb956508c9d94935bedba4f13901fb2b7468e91
commit: 498d5b14db8c9118be139f668720c67bea2dc344 riscv: selftests: Fix warnings pointer masking test
date: 10 months ago
:::::: branch date: 3 hours ago
:::::: commit date: 10 months ago
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20251026/202510260342.qQLArXOY-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251026/202510260342.qQLArXOY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202510260342.qQLArXOY-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> pointer_masking.c:216:25: warning: format string is not a string literal (potentially insecure) [-Wformat-security]
216 | ksft_test_result_fail(err_pwrite_msg);
| ^~~~~~~~~~~~~~
pointer_masking.c:216:25: note: treat the string as an argument to avoid this
216 | ksft_test_result_fail(err_pwrite_msg);
| ^
| "%s",
pointer_masking.c:223:25: warning: format string is not a string literal (potentially insecure) [-Wformat-security]
223 | ksft_test_result_fail(err_pwrite_msg);
| ^~~~~~~~~~~~~~
pointer_masking.c:223:25: note: treat the string as an argument to avoid this
223 | ksft_test_result_fail(err_pwrite_msg);
| ^
| "%s",
2 warnings generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-10-25 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 19:16 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-26 5:50 pointer_masking.c:216:25: warning: format string is not a string literal (potentially insecure) kernel test robot
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=202510260342.qQLArXOY-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.