From: Will Deacon <will@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
catalin.marinas@arm.com, keescook@chromium.org,
masahiroy@kernel.org, vincenzo.frascino@arm.com
Subject: Re: [PATCH v5 0/4] Enable orphan-handling=warn for VDSO
Date: Thu, 23 Jun 2022 18:53:53 +0100 [thread overview]
Message-ID: <20220623175352.GA17471@willie-the-truck> (raw)
In-Reply-To: <20220510095834.32394-1-joey.gouly@arm.com>
Hi Joey,
On Tue, May 10, 2022 at 10:58:30AM +0100, Joey Gouly wrote:
> This small series enables the orphan-handling linker flag for the VDSO.
> This could catch subtle errors if features that use special sections are
> introduced into the VDSO implementation.
>
> Tested by running the VDSO self tests.
> Tested building with LLVM LLD and Binutils LD linkers.
I've applied this locally, but I'm seeing a warning from LLD when linking
the 32-bit vDSO object:
| LD32 arch/arm64/kernel/vdso32/vdso.so.raw
| ld.lld: warning: <internal>:(.ARM.exidx) is being placed in '.ARM.exidx'
Please can you take a look and send an additional patch on top to fix this?
Thanks,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-23 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:58 [PATCH v5 0/4] Enable orphan-handling=warn for VDSO Joey Gouly
2022-05-10 9:58 ` [PATCH v5 1/4] arm64: vdso: put ELF related sections in the linker script Joey Gouly
2022-05-10 10:39 ` Vincenzo Frascino
2022-05-10 9:58 ` [PATCH v5 2/4] arm64: vdso: enable orphan handling for VDSO Joey Gouly
2022-05-10 9:58 ` [PATCH v5 3/4] arm64: vdso32: put ELF related sections in the linker script Joey Gouly
2022-05-10 9:58 ` [PATCH v5 4/4] arm64: vdso32: enable orphan handling for VDSO Joey Gouly
2022-06-23 17:53 ` Will Deacon [this message]
2022-06-23 18:05 ` [PATCH v5 0/4] Enable orphan-handling=warn " Joey Gouly
2022-06-23 19:34 ` Will Deacon
2022-06-23 19:31 ` Will Deacon
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=20220623175352.GA17471@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=nd@arm.com \
--cc=vincenzo.frascino@arm.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