From: kernel test robot <lkp@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 13240/13245] powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data279' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data279'
Date: Fri, 12 Jan 2024 08:27:04 +0800 [thread overview]
Message-ID: <202401120827.fAJNcWMO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 9e21984d62c56a0f6d1fc6f76b646212cfd7fe88
commit: 7511709cfbd438b90467726e4c107edf5b53815c [13240/13245] Merge branch 'bitmap-for-next' of https://github.com/norov/linux.git
config: powerpc-buildonly-randconfig-r002-20230209 (https://download.01.org/0day-ci/archive/20240112/202401120827.fAJNcWMO-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/20240112/202401120827.fAJNcWMO-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/202401120827.fAJNcWMO-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data279' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data279'
>> powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data279' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data279'
>> powerpc-linux-ld: warning: orphan section `.bss..Lubsan_data279' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data279'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-12 0:27 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=202401120827.fAJNcWMO-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yury.norov@gmail.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