From: kernel test robot <lkp@intel.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>
Subject: powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data150' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data150'
Date: Sat, 6 Apr 2024 23:20:21 +0800 [thread overview]
Message-ID: <202404062331.U6Dreg68-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6c6e47d69d821047097909288b6d7f1aafb3b9b1
commit: f568a3d49af9aed813a184353592efe29b0e3d16 bpf,lsm: Add BPF token LSM hooks
date: 2 months ago
config: powerpc-randconfig-r035-20220327 (https://download.01.org/0day-ci/archive/20240406/202404062331.U6Dreg68-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240406/202404062331.U6Dreg68-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/202404062331.U6Dreg68-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data150' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data150'
>> powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data150' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data150'
>> powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data150' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data150'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-06 15:20 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=202404062331.U6Dreg68-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.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 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.