All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	Szabolcs Nagy <szabolcs.nagy@arm.com>,
	Jeremy Linton <jeremy.linton@arm.com>,
	"H . J . Lu" <hjl.tools@gmail.com>,
	Yu-cheng Yu <yu-cheng.yu@intel.com>,
	linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	libc-alpha@sourceware.org, Dave Martin <Dave.Martin@arm.com>
Subject: Re: [PATCH v8 3/4] elf: Remove has_interp property from arch_adjust_elf_prot()
Date: Fri, 4 Feb 2022 14:53:55 +0000	[thread overview]
Message-ID: <Yf0+A805DZdD3gwy@arm.com> (raw)
In-Reply-To: <20220124150704.2559523-4-broonie@kernel.org>

On Mon, Jan 24, 2022 at 03:07:03PM +0000, Mark Brown wrote:
> Since we have added an is_interp flag to arch_parse_elf_property() we can
> drop the has_interp flag from arch_elf_adjust_prot(), the only user was
> the arm64 code which no longer needs it and any future users will be able
> to use arch_parse_elf_properties() to determine if an interpreter is in
> use.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Tested-by: Jeremy Linton <jeremy.linton@arm.com>
> Reviewed-By: Dave Martin <Dave.Martin@arm.com>

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	Szabolcs Nagy <szabolcs.nagy@arm.com>,
	Jeremy Linton <jeremy.linton@arm.com>,
	"H . J . Lu" <hjl.tools@gmail.com>,
	Yu-cheng Yu <yu-cheng.yu@intel.com>,
	linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	libc-alpha@sourceware.org, Dave Martin <Dave.Martin@arm.com>
Subject: Re: [PATCH v8 3/4] elf: Remove has_interp property from arch_adjust_elf_prot()
Date: Fri, 4 Feb 2022 14:53:55 +0000	[thread overview]
Message-ID: <Yf0+A805DZdD3gwy@arm.com> (raw)
In-Reply-To: <20220124150704.2559523-4-broonie@kernel.org>

On Mon, Jan 24, 2022 at 03:07:03PM +0000, Mark Brown wrote:
> Since we have added an is_interp flag to arch_parse_elf_property() we can
> drop the has_interp flag from arch_elf_adjust_prot(), the only user was
> the arm64 code which no longer needs it and any future users will be able
> to use arch_parse_elf_properties() to determine if an interpreter is in
> use.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Tested-by: Jeremy Linton <jeremy.linton@arm.com>
> Reviewed-By: Dave Martin <Dave.Martin@arm.com>

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-02-04 14:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 15:07 [PATCH v8 0/4] arm64: Enable BTI for the executable as well as the interpreter Mark Brown
2022-01-24 15:07 ` Mark Brown
2022-01-24 15:07 ` [PATCH v8 1/4] elf: Allow architectures to parse properties on the main executable Mark Brown
2022-01-24 15:07   ` Mark Brown
2022-02-04 13:00   ` Catalin Marinas
2022-02-04 13:00     ` Catalin Marinas
2022-01-24 15:07 ` [PATCH v8 2/4] arm64: Enable BTI for main executable as well as the interpreter Mark Brown
2022-01-24 15:07   ` Mark Brown
2022-02-04 13:11   ` Catalin Marinas
2022-02-04 13:11     ` Catalin Marinas
2022-01-24 15:07 ` [PATCH v8 3/4] elf: Remove has_interp property from arch_adjust_elf_prot() Mark Brown
2022-01-24 15:07   ` Mark Brown
2022-02-04 14:53   ` Catalin Marinas [this message]
2022-02-04 14:53     ` Catalin Marinas
2022-01-24 15:07 ` [PATCH v8 4/4] elf: Remove has_interp property from arch_parse_elf_property() Mark Brown
2022-01-24 15:07   ` Mark Brown
2022-02-04 14:54   ` Catalin Marinas
2022-02-04 14:54     ` Catalin Marinas
2022-02-15 18:34 ` [PATCH v8 0/4] arm64: Enable BTI for the executable as well as the interpreter Will Deacon
2022-02-15 18:34   ` Will Deacon
2022-02-16 13:34   ` Catalin Marinas
2022-02-16 13:34     ` Catalin Marinas
2022-02-16 16:49     ` Szabolcs Nagy
2022-02-16 16:49       ` Szabolcs Nagy
2022-02-16 17:01       ` Mark Brown
2022-02-16 17:01         ` Mark Brown
2022-02-17  8:17         ` Szabolcs Nagy
2022-02-17  8:17           ` Szabolcs Nagy
2022-02-22 14:15     ` Mark Brown
2022-02-22 14:15       ` Mark Brown
2022-02-25 13:53     ` Will Deacon
2022-02-25 13:53       ` Will Deacon
2022-02-25 15:11       ` Mark Brown
2022-02-25 15:11         ` Mark Brown
2022-02-25 15:54         ` Will Deacon
2022-02-25 15:54           ` 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=Yf0+A805DZdD3gwy@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=broonie@kernel.org \
    --cc=hjl.tools@gmail.com \
    --cc=jeremy.linton@arm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=szabolcs.nagy@arm.com \
    --cc=will@kernel.org \
    --cc=yu-cheng.yu@intel.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 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.