From: Kees Cook <keescook@chromium.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 2/2] arm64/build: Warn on orphan section placement
Date: Tue, 23 Jun 2020 21:41:05 -0700 [thread overview]
Message-ID: <202006232140.BD988273@keescook> (raw)
In-Reply-To: <202006241159.zO6bF0Gp%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]
On Wed, Jun 24, 2020 at 11:52:33AM +0800, kernel test robot wrote:
> Hi Kees,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on arm64/for-next/core]
> [cannot apply to arm-perf/for-next/perf]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use as documented in
> https://git-scm.com/docs/git-format-patch]
>
> url: https://github.com/0day-ci/linux/commits/Kees-Cook/arm64-Warn-on-orphan-section-placement/20200623-050132
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> config: arm64-randconfig-r003-20200623 (attached as .config)
> compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 1d4c87335d5236ea1f35937e1014980ba961ae34)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install arm64 cross compiling tool for clang build
> # apt-get install binutils-aarch64-linux-gnu
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> ld.lld: warning: arch/arm64/built-in.a(mm/mmu.o):(".mmuoff.data.write") is being placed in '".mmuoff.data.write"'
> ld.lld: warning: ./drivers/firmware/efi/libstub/lib.a(arm-stub.stub.o):(.init.note.gnu.property) is being placed in '.init.note.gnu.property'
Thanks! This is all fixed in the v3 series now:
https://lore.kernel.org/lkml/20200624014940.1204448-1-keescook(a)chromium.org/
--
Kees Cook
prev parent reply other threads:[~2020-06-24 4:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:58 [PATCH v2 0/2] arm64: Warn on orphan section placement Kees Cook
2020-06-22 20:58 ` [PATCH v2 1/2] arm64/build: Use common DISCARDS in linker script Kees Cook
2020-06-22 20:58 ` [PATCH v2 2/2] arm64/build: Warn on orphan section placement Kees Cook
2020-06-23 14:52 ` Will Deacon
2020-06-23 14:52 ` Will Deacon
2020-06-23 14:59 ` Ard Biesheuvel
2020-06-23 14:59 ` Ard Biesheuvel
2020-06-23 19:18 ` Nick Desaulniers
2020-06-23 19:18 ` Nick Desaulniers
2020-06-23 21:06 ` Kees Cook
2020-06-23 21:06 ` Kees Cook
2020-06-23 21:21 ` Ard Biesheuvel
2020-06-23 21:21 ` Ard Biesheuvel
2020-06-24 0:05 ` Kees Cook
2020-06-24 0:05 ` Kees Cook
2020-06-24 3:52 ` kernel test robot
2020-06-24 4:41 ` Kees Cook [this message]
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=202006232140.BD988273@keescook \
--to=keescook@chromium.org \
--cc=kbuild-all@lists.01.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 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.