From: kernel test robot <lkp@intel.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrii Nakryiko <andrii@kernel.org>
Subject: [linux-next:master 7010/8016] tools/lib/bpf/btf_relocate.c:61:25: sparse: sparse: dubious one-bit signed bitfield
Date: Tue, 25 Jun 2024 08:26:17 +0800 [thread overview]
Message-ID: <202406250808.rsBmro61-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 62c97045b8f720c2eac807a5f38e26c9ed512371
commit: 8646db238997df36c6ad71a9d7e0b52ceee221b2 [7010/8016] libbpf,bpf: Share BTF relocate-related code with kernel
config: x86_64-randconfig-123-20240624 (https://download.01.org/0day-ci/archive/20240625/202406250808.rsBmro61-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240625/202406250808.rsBmro61-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/oe-kbuild-all/202406250808.rsBmro61-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> tools/lib/bpf/btf_relocate.c:61:25: sparse: sparse: dubious one-bit signed bitfield
vim +61 tools/lib/bpf/btf_relocate.c
19e00c897d5031 Alan Maguire 2024-06-13 56
19e00c897d5031 Alan Maguire 2024-06-13 57 /* <name, size, id> triple used in sorting/searching distilled base BTF. */
19e00c897d5031 Alan Maguire 2024-06-13 58 struct btf_name_info {
19e00c897d5031 Alan Maguire 2024-06-13 59 const char *name;
19e00c897d5031 Alan Maguire 2024-06-13 60 /* set when search requires a size match */
19e00c897d5031 Alan Maguire 2024-06-13 @61 int needs_size:1,
19e00c897d5031 Alan Maguire 2024-06-13 62 size:31;
19e00c897d5031 Alan Maguire 2024-06-13 63 __u32 id;
19e00c897d5031 Alan Maguire 2024-06-13 64 };
19e00c897d5031 Alan Maguire 2024-06-13 65
:::::: The code at line 61 was first introduced by commit
:::::: 19e00c897d5031bed969dd79af28e899e038009f libbpf: Split BTF relocation
:::::: TO: Alan Maguire <alan.maguire@oracle.com>
:::::: CC: Andrii Nakryiko <andrii@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-25 0:26 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=202406250808.rsBmro61-lkp@intel.com \
--to=lkp@intel.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@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