From: Joey Gouly <joey.gouly@arm.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: <nd@arm.com>, <catalin.marinas@arm.com>, <joey.gouly@arm.com>,
<keescook@chromium.org>, <masahiroy@kernel.org>,
<vincenzo.frascino@arm.com>, <will@kernel.org>
Subject: [PATCH v3 0/4] Enable orphan-handling=warn for VDSO
Date: Wed, 13 Apr 2022 11:18:28 +0100 [thread overview]
Message-ID: <20220413101832.4594-1-joey.gouly@arm.com> (raw)
Hi all,
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.
Changes from v2 [1]:
- Include vdso compat support
Thanks,
Joey
[1]: https://lore.kernel.org/linux-arm-kernel/20220407101304.539-1-joey.gouly@arm.com/
Joey Gouly (4):
arm64: vdso: put ELF related sections in the linker script
arm64: vdso: enable orphan handling for VDSO
arm64: vdso32: put ELF related sections in the linker script
arm64: vdso32: enable orphan handling for VDSO
arch/arm64/kernel/vdso/Makefile | 8 +++++++-
arch/arm64/kernel/vdso/vdso.lds.S | 4 ++++
arch/arm64/kernel/vdso32/Makefile | 1 +
arch/arm64/kernel/vdso32/vdso.lds.S | 4 ++++
4 files changed, 16 insertions(+), 1 deletion(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-13 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 10:18 Joey Gouly [this message]
2022-04-13 10:18 ` [PATCH v3 1/4] arm64: vdso: put ELF related sections in the linker script Joey Gouly
2022-04-13 10:18 ` [PATCH v3 2/4] arm64: vdso: enable orphan handling for VDSO Joey Gouly
2022-04-13 10:18 ` [PATCH v3 3/4] arm64: vdso32: put ELF related sections in the linker script Joey Gouly
2022-04-13 10:18 ` [PATCH v3 4/4] arm64: vdso32: enable orphan handling for VDSO Joey Gouly
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=20220413101832.4594-1-joey.gouly@arm.com \
--to=joey.gouly@arm.com \
--cc=catalin.marinas@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 \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).