All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dave Martin <Dave.Martin@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Topi Miettinen <toiwoton@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Salvatore Mesoraca <s.mesoraca16@gmail.com>,
	systemd-devel@lists.freedesktop.org,
	Kees Cook <keescook@chromium.org>,
	kernel-hardening@lists.openwall.com,
	Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeremy Linton <jeremy.linton@arm.com>,
	linux-hardening@vger.kernel.org, libc-alpha@sourceware.org,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: BTI interaction between seccomp filters in systemd and glibc mprotect calls, causing service failures
Date: Mon, 26 Oct 2020 16:51:25 +0000	[thread overview]
Message-ID: <20201026165125.GF7402@sirena.org.uk> (raw)
In-Reply-To: <20201026155628.GA27285@arm.com>

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

On Mon, Oct 26, 2020 at 03:56:35PM +0000, Dave Martin wrote:
> On Mon, Oct 26, 2020 at 02:52:46PM +0000, Catalin Marinas via Libc-alpha wrote:

> > Now, if the dynamic loader silently ignores the mprotect() failure on
> > the main executable, is there much value in exposing a flag in the aux
> > vectors? It saves a few (one?) mprotect() calls but I don't think it
> > matters much. Anyway, I don't mind the flag.

> I don't see a problem with the aforementioned patch [2] to pre-set BTI
> on the pages of the main binary.

Me either FWIW.

[-- 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: Dave Martin <Dave.Martin@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Salvatore Mesoraca <s.mesoraca16@gmail.com>,
	systemd-devel@lists.freedesktop.org,
	Kees Cook <keescook@chromium.org>,
	kernel-hardening@lists.openwall.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeremy Linton <jeremy.linton@arm.com>,
	Topi Miettinen <toiwoton@gmail.com>,
	linux-hardening@vger.kernel.org, libc-alpha@sourceware.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: BTI interaction between seccomp filters in systemd and glibc mprotect calls, causing service failures
Date: Mon, 26 Oct 2020 16:51:25 +0000	[thread overview]
Message-ID: <20201026165125.GF7402@sirena.org.uk> (raw)
In-Reply-To: <20201026155628.GA27285@arm.com>


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

On Mon, Oct 26, 2020 at 03:56:35PM +0000, Dave Martin wrote:
> On Mon, Oct 26, 2020 at 02:52:46PM +0000, Catalin Marinas via Libc-alpha wrote:

> > Now, if the dynamic loader silently ignores the mprotect() failure on
> > the main executable, is there much value in exposing a flag in the aux
> > vectors? It saves a few (one?) mprotect() calls but I don't think it
> > matters much. Anyway, I don't mind the flag.

> I don't see a problem with the aforementioned patch [2] to pre-set BTI
> on the pages of the main binary.

Me either FWIW.

[-- 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:[~2020-10-26 16:52 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8584c14f-5c28-9d70-c054-7c78127d84ea@arm.com>
2020-10-22  7:18 ` [systemd-devel] BTI interaction between seccomp filters in systemd and glibc mprotect calls, causing service failures Lennart Poettering
2020-10-22  7:18   ` Lennart Poettering
2020-10-22  7:54   ` Florian Weimer
2020-10-22  7:54     ` Florian Weimer
2020-10-22  8:17     ` Topi Miettinen
2020-10-22  8:17       ` Topi Miettinen
2020-10-22  8:25       ` Florian Weimer
2020-10-22  8:25         ` Florian Weimer
2020-10-22  8:29       ` Szabolcs Nagy
2020-10-22  8:29         ` Szabolcs Nagy
2020-10-22  8:38         ` Lennart Poettering
2020-10-22  8:38           ` Lennart Poettering
2020-10-22  9:31           ` Catalin Marinas
2020-10-22  9:31             ` Catalin Marinas
2020-10-22 10:12             ` Topi Miettinen
2020-10-22 10:12               ` Topi Miettinen
2020-10-22 10:27               ` Florian Weimer
2020-10-22 10:27                 ` Florian Weimer
2020-10-23  6:13             ` Szabolcs Nagy
2020-10-23  6:13               ` Szabolcs Nagy
2020-10-23  9:04               ` Catalin Marinas
2020-10-23  9:04                 ` Catalin Marinas
2020-10-22 10:03         ` Topi Miettinen
2020-10-22 10:03           ` Topi Miettinen
2020-10-22  8:05   ` Szabolcs Nagy
2020-10-22  8:05     ` Szabolcs Nagy
2020-10-22  8:31     ` Lennart Poettering
2020-10-22  8:31       ` Lennart Poettering
     [not found] ` <20201022075447.GO3819@arm.com>
2020-10-22 10:39   ` Topi Miettinen
2020-10-22 10:39     ` Topi Miettinen
2020-10-22 20:02     ` Kees Cook
2020-10-22 20:02       ` Kees Cook
2020-10-22 20:02       ` Kees Cook
2020-10-22 22:24       ` Topi Miettinen
2020-10-22 22:24         ` Topi Miettinen
2020-10-22 22:24         ` Topi Miettinen
2020-10-23 17:52         ` Salvatore Mesoraca
2020-10-23 17:52           ` Salvatore Mesoraca
2020-10-23 17:52           ` Salvatore Mesoraca
2020-10-24 11:34           ` Topi Miettinen
2020-10-24 11:34             ` Topi Miettinen
2020-10-24 11:34             ` Topi Miettinen
2020-10-24 14:12             ` Salvatore Mesoraca
2020-10-24 14:12               ` Salvatore Mesoraca
2020-10-24 14:12               ` Salvatore Mesoraca
2020-10-25 13:42               ` Jordan Glover
2020-10-25 13:42                 ` Jordan Glover
2020-10-25 13:42                 ` Jordan Glover
2020-10-23  9:02       ` Catalin Marinas
2020-10-23  9:02         ` Catalin Marinas
2020-10-23  9:02         ` Catalin Marinas
2020-10-24 11:01         ` Topi Miettinen
2020-10-24 11:01           ` Topi Miettinen
2020-10-24 11:01           ` Topi Miettinen
2020-10-26 14:52           ` Catalin Marinas
2020-10-26 14:52             ` Catalin Marinas
2020-10-26 14:52             ` Catalin Marinas
2020-10-26 15:56             ` Dave Martin
2020-10-26 15:56               ` Dave Martin
2020-10-26 15:56               ` Dave Martin
2020-10-26 16:51               ` Mark Brown [this message]
2020-10-26 16:51                 ` Mark Brown
2020-10-26 16:51                 ` Mark Brown
2020-10-26 16:31             ` Topi Miettinen
2020-10-26 16:31               ` Topi Miettinen
2020-10-26 16:31               ` Topi Miettinen
2020-10-26 16:24 ` Dave Martin
2020-10-26 16:24   ` Dave Martin
2020-10-26 16:39   ` Topi Miettinen
2020-10-26 16:39     ` Topi Miettinen
2020-10-26 16:45   ` Florian Weimer
2020-10-26 16:45     ` Florian Weimer
2020-10-27 14:22     ` Dave Martin
2020-10-27 14:22       ` Dave Martin
2020-10-27 14:41       ` Florian Weimer
2020-10-27 14:41         ` Florian Weimer
2020-10-26 16:57   ` Szabolcs Nagy
2020-10-26 16:57     ` Szabolcs Nagy
2020-10-26 17:52     ` Dave Martin
2020-10-26 17:52       ` Dave Martin
2020-10-26 22:39       ` Jeremy Linton
2020-10-26 22:39         ` Jeremy Linton
2020-10-27 14:15         ` Dave Martin
2020-10-27 14:15           ` Dave Martin
2020-10-29 11:02           ` Catalin Marinas
2020-10-29 11:02             ` Catalin Marinas
2020-11-04 12:18             ` Dave Martin
2020-11-04 12:18               ` Dave Martin

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=20201026165125.GF7402@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Dave.Martin@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=jeremy.linton@arm.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=s.mesoraca16@gmail.com \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=toiwoton@gmail.com \
    --cc=will.deacon@arm.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.