From: Kees Cook <keescook@chromium.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
catalin.marinas@arm.com, masahiroy@kernel.org,
vincenzo.frascino@arm.com, will@kernel.org
Subject: Re: [PATCH v4 4/4] arm64: vdso32: enable orphan handling for VDSO
Date: Thu, 14 Apr 2022 10:22:54 -0700 [thread overview]
Message-ID: <202204141022.4236FAAD3E@keescook> (raw)
In-Reply-To: <20220414104611.17748-5-joey.gouly@arm.com>
On Thu, Apr 14, 2022 at 11:46:11AM +0100, Joey Gouly wrote:
> Like vmlinux, enable orphan-handling for the compat VDSO32. This can catch
> subtle errors that might arise from unexpected sections being included.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
_______________________________________________
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-04-14 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 10:46 [PATCH v4 0/4] Enable orphan-handling=warn for VDSO Joey Gouly
2022-04-14 10:46 ` [PATCH v4 1/4] arm64: vdso: put ELF related sections in the linker script Joey Gouly
2022-04-14 10:46 ` [PATCH v4 2/4] arm64: vdso: enable orphan handling for VDSO Joey Gouly
2022-04-14 10:46 ` [PATCH v4 3/4] arm64: vdso32: put ELF related sections in the linker script Joey Gouly
2022-04-14 17:22 ` Kees Cook
2022-04-19 11:00 ` Vincenzo Frascino
2022-04-14 10:46 ` [PATCH v4 4/4] arm64: vdso32: enable orphan handling for VDSO Joey Gouly
2022-04-14 17:22 ` Kees Cook [this message]
2022-04-19 11:01 ` Vincenzo Frascino
2022-04-19 11:10 ` [PATCH v4 0/4] Enable orphan-handling=warn " Vincenzo Frascino
2022-04-19 12:16 ` Joey Gouly
2022-04-19 12:53 ` Vincenzo Frascino
2022-04-27 18:20 ` Catalin Marinas
2022-04-28 16:11 ` 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=202204141022.4236FAAD3E@keescook \
--to=keescook@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--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).