From: Yury Norov <yury.norov@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Changbin Du <changbin.du@huawei.com>
Subject: Re: [linux-next:master 9918/9925] powerpc64-linux-ld: warning: orphan section `.bss..Lubsan_data794' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data794'
Date: Mon, 25 Dec 2023 09:19:19 -0800 [thread overview]
Message-ID: <ZYm5l6AIMVMs69RC@yury-ThinkPad> (raw)
In-Reply-To: <202312230642.EBF6kiYY-lkp@intel.com>
On Sat, Dec 23, 2023 at 06:15:23AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 39676dfe52331dba909c617f213fdb21015c8d10
> commit: c6aa10bc7b8bfcfaca4311ac5f39b4d6eb5b1ccf [9918/9925] Merge branch 'bitmap-for-next' of https://github.com/norov/linux.git
> config: powerpc64-randconfig-r035-20211208 (https://download.01.org/0day-ci/archive/20231223/202312230642.EBF6kiYY-lkp@intel.com/config)
> compiler: powerpc64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231223/202312230642.EBF6kiYY-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/202312230642.EBF6kiYY-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> powerpc64-linux-ld: warning: orphan section `.bss..Lubsan_data794' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data794'
> powerpc64-linux-ld: warning: discarding dynamic section .glink
> powerpc64-linux-ld: warning: discarding dynamic section .plt
> powerpc64-linux-ld: linkage table error against `flush_module_init_free_work'
> powerpc64-linux-ld: stubs don't match calculated size
> powerpc64-linux-ld: can not build stubs: bad value
> powerpc64-linux-ld: init/main.o: in function `kernel_init':
> main.c:(.ref.text+0x224): undefined reference to `flush_module_init_free_work'
+ Stephen Rothwell, Changbin Du
So, it looks misattributed, and already fixed in 9a63d5058dd3545?
Thanks,
Yury
next prev parent reply other threads:[~2023-12-25 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 22:15 [linux-next:master 9918/9925] powerpc64-linux-ld: warning: orphan section `.bss..Lubsan_data794' from `kernel/ptrace.o' being placed in section `.bss..Lubsan_data794' kernel test robot
2023-12-25 17:19 ` Yury Norov [this message]
2023-12-26 2:16 ` Changbin Du
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=ZYm5l6AIMVMs69RC@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=changbin.du@huawei.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
/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.