From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: elf.h: Correct comment about READ_IMPLIES_EXEC propagation
Date: Mon, 9 Oct 2017 10:00:11 +0100 [thread overview]
Message-ID: <20171009090010.GA5127@arm.com> (raw)
In-Reply-To: <20171006020001.GD2971@decadent.org.uk>
On Fri, Oct 06, 2017 at 03:00:01AM +0100, Ben Hutchings wrote:
> Process personality always propagates across a fork(), but can change
> at an execve().
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> arch/arm64/include/asm/elf.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
You're right, the comment is sloppy. I'll pick this up for 4.15.
Will
> diff --git a/arch/arm64/include/asm/elf.h b/arch/arm64/include/asm/elf.h
> index 33be513ef24c..fac1c4de7898 100644
> --- a/arch/arm64/include/asm/elf.h
> +++ b/arch/arm64/include/asm/elf.h
> @@ -188,8 +188,8 @@ typedef compat_elf_greg_t compat_elf_gregset_t[COMPAT_ELF_NGREG];
>
> #define compat_start_thread compat_start_thread
> /*
> - * Unlike the native SET_PERSONALITY macro, the compat version inherits
> - * READ_IMPLIES_EXEC across a fork() since this is the behaviour on
> + * Unlike the native SET_PERSONALITY macro, the compat version maintains
> + * READ_IMPLIES_EXEC across an execve() since this is the behaviour on
> * arch/arm/.
> */
> #define COMPAT_SET_PERSONALITY(ex) \
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2017-10-09 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 2:00 [PATCH] arm64: elf.h: Correct comment about READ_IMPLIES_EXEC propagation Ben Hutchings
2017-10-09 9:00 ` Will Deacon [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=20171009090010.GA5127@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).