All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Kees Cook <keescook@chromium.org>,
	linux-arm-kernel@lists.infradead.org, hjl.tools@gmail.com,
	libc-alpha@sourceware.org, szabolcs.nagy@arm.com,
	yu-cheng.yu@intel.com, ebiederm@xmission.com,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH v13 0/2] arm64: Enable BTI for the executable as well as the interpreter
Date: Thu, 21 Apr 2022 18:58:58 +0100	[thread overview]
Message-ID: <YmGbYsZVsQMoM9xR@sirena.org.uk> (raw)
In-Reply-To: <52a79b24-deec-108e-4b7f-5bc33500c802@arm.com>

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

On Thu, Apr 21, 2022 at 10:52:52AM -0500, Jeremy Linton wrote:

> Or maybe simpler yet, we provide a tool which wipes out the gnu BTI note on
> binaries that are found to have BTI bugs, thereby (correctly) fixing the
> problem at its source. This is at least presumably doable if we are also
> assuming we can update glibc/etc in any environment with the problem.

This seems like the most sensible thing if we do find we're running into
BTI executables that are incorrectly annotated and difficult to fix - it
avoids having to manage any new permissions for bypassing BTI.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Kees Cook <keescook@chromium.org>,
	linux-arm-kernel@lists.infradead.org, hjl.tools@gmail.com,
	libc-alpha@sourceware.org, szabolcs.nagy@arm.com,
	yu-cheng.yu@intel.com, ebiederm@xmission.com,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH v13 0/2] arm64: Enable BTI for the executable as well as the interpreter
Date: Thu, 21 Apr 2022 18:58:58 +0100	[thread overview]
Message-ID: <YmGbYsZVsQMoM9xR@sirena.org.uk> (raw)
In-Reply-To: <52a79b24-deec-108e-4b7f-5bc33500c802@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 574 bytes --]

On Thu, Apr 21, 2022 at 10:52:52AM -0500, Jeremy Linton wrote:

> Or maybe simpler yet, we provide a tool which wipes out the gnu BTI note on
> binaries that are found to have BTI bugs, thereby (correctly) fixing the
> problem at its source. This is at least presumably doable if we are also
> assuming we can update glibc/etc in any environment with the problem.

This seems like the most sensible thing if we do find we're running into
BTI executables that are incorrectly annotated and difficult to fix - it
avoids having to manage any new permissions for bypassing BTI.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

  reply	other threads:[~2022-04-21 17:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 10:51 [PATCH v13 0/2] arm64: Enable BTI for the executable as well as the interpreter Mark Brown
2022-04-19 10:51 ` Mark Brown
2022-04-19 10:51 ` [PATCH v13 1/2] elf: Allow architectures to parse properties on the main executable Mark Brown
2022-04-19 10:51   ` Mark Brown
2022-04-20 16:51   ` Kees Cook
2022-04-20 16:51     ` Kees Cook
2022-04-19 10:51 ` [PATCH v13 2/2] arm64: Enable BTI for main executable as well as the interpreter Mark Brown
2022-04-19 10:51   ` Mark Brown
2022-04-20  5:33 ` [PATCH v13 0/2] arm64: Enable BTI for the " Kees Cook
2022-04-20  5:33   ` Kees Cook
2022-04-20  9:36   ` Will Deacon
2022-04-20  9:36     ` Will Deacon
2022-04-20  9:57     ` Catalin Marinas
2022-04-20  9:57       ` Catalin Marinas
2022-04-20 11:57       ` Mark Brown
2022-04-20 11:57         ` Mark Brown
2022-04-20 13:39         ` Jeremy Linton
2022-04-20 13:39           ` Jeremy Linton
2022-04-20 16:51           ` Kees Cook
2022-04-20 16:51             ` Kees Cook
2022-04-21  9:34           ` Catalin Marinas
2022-04-21  9:34             ` Catalin Marinas
2022-04-21 15:52             ` Jeremy Linton
2022-04-21 15:52               ` Jeremy Linton
2022-04-21 17:58               ` Mark Brown [this message]
2022-04-21 17:58                 ` Mark Brown
2022-04-20 16:48     ` Kees Cook
2022-04-20 16:48       ` Kees Cook
2022-04-20 16:51   ` Kees Cook
2022-04-20 16:51     ` Kees Cook

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=YmGbYsZVsQMoM9xR@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=ebiederm@xmission.com \
    --cc=hjl.tools@gmail.com \
    --cc=jeremy.linton@arm.com \
    --cc=keescook@chromium.org \
    --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.