From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: srv6_mobile_send.c:60:18: warning: 'plen' may be used uninitialized
Date: Sat, 11 Jul 2026 03:29:04 +0200 [thread overview]
Message-ID: <202607110359.ePqo7PmV-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
:::::: Manual check reason: "likely FALSE maybe-used-uninitialized warning on old compiler"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Yuya Kusakabe <yuya.kusakabe@gmail.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Yuya-Kusakabe/seg6-add-support-for-the-SRv6-End-MAP-behavior/20260710-171238
head: 15a633eda320fd75c637aca18deb3620faa75214
commit: 15a633eda320fd75c637aca18deb3620faa75214 selftests: seg6: add selftest for End.MAP behavior
date: 16 hours ago
:::::: branch date: 16 hours ago
:::::: commit date: 16 hours ago
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260711/202607110359.ePqo7PmV-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260711/202607110359.ePqo7PmV-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/202607110359.ePqo7PmV-lkp@intel.com/
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
srv6_mobile_send.c: In function 'main':
>> srv6_mobile_send.c:60:18: warning: 'plen' may be used uninitialized [-Wmaybe-uninitialized]
60 | uint32_t plen = htonl(len);
| ^~~~
>> srv6_mobile_send.c:59:18: warning: 'nexthdr' may be used uninitialized [-Wmaybe-uninitialized]
59 | uint32_t nexthdr = htonl(IPPROTO_ICMPV6);
| ^~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-11 1:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607110359.ePqo7PmV-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox