From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: [tip:sched/core 4/45] riscv64-linux-ld: warning: orphan section `.bss..Lubsan_data645' from `kernel/sched/core.o' being placed in section `.bss..Lubsan_data645'
Date: Tue, 24 Oct 2023 12:25:02 +0800 [thread overview]
Message-ID: <202310241201.kBVQXuBP-lkp@intel.com> (raw)
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head: 4e5b65a22ba0cabe58f895cd797cb10a763d6994
commit: 7a50f76674f8b6f4f30a1cec954179f10e20110c [4/45] sched: Simplify yield_to()
config: riscv-randconfig-002-20230923 (https://download.01.org/0day-ci/archive/20231024/202310241201.kBVQXuBP-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231024/202310241201.kBVQXuBP-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/202310241201.kBVQXuBP-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> riscv64-linux-ld: warning: orphan section `.bss..Lubsan_data645' from `kernel/sched/core.o' being placed in section `.bss..Lubsan_data645'
>> riscv64-linux-ld: warning: orphan section `.bss..Lubsan_data645' from `kernel/sched/core.o' being placed in section `.bss..Lubsan_data645'
>> riscv64-linux-ld: warning: orphan section `.bss..Lubsan_data645' from `kernel/sched/core.o' being placed in section `.bss..Lubsan_data645'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-24 4:25 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=202310241201.kBVQXuBP-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®