From: Florian Weimer <fweimer@redhat.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
Jeremy Linton <jeremy.linton@arm.com>,
Mark Brown <broonie@kernel.org>,
libc-alpha@sourceware.org, Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
Kees Cook <keescook@chromium.org>,
Salvatore Mesoraca <s.mesoraca16@gmail.com>,
Lennart Poettering <mzxreary@0pointer.de>,
Topi Miettinen <toiwoton@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-hardening@lists.openwall.com,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH 0/4] aarch64: avoid mprotect(PROT_BTI|PROT_EXEC) [BZ #26831]
Date: Wed, 04 Nov 2020 15:45:44 +0100 [thread overview]
Message-ID: <87ft5p2naf.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20201104144120.GD28902@gaia> (Catalin Marinas's message of "Wed, 4 Nov 2020 14:41:21 +0000")
* Catalin Marinas:
> Can the dynamic loader mmap() the main exe again while munmap'ing the
> original one? (sorry if it was already discussed)
No, we don't have a descriptor for that. /proc may not be mounted, and
using the path stored there has a race condition anyway.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-11-04 14:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:25 [PATCH 0/4] aarch64: avoid mprotect(PROT_BTI|PROT_EXEC) [BZ #26831] Szabolcs Nagy
2020-11-03 10:25 ` [PATCH 1/4] elf: Pass the fd to note processing " Szabolcs Nagy
2020-11-03 10:26 ` [PATCH 2/4] elf: Move note processing after l_phdr is updated " Szabolcs Nagy
2020-11-03 10:38 ` Florian Weimer
2020-11-03 12:36 ` H.J. Lu
2020-11-03 15:04 ` Szabolcs Nagy
2020-11-03 15:27 ` H.J. Lu
2020-11-03 10:26 ` [PATCH 3/4] aarch64: Use mmap to add PROT_BTI instead of mprotect " Szabolcs Nagy
2020-11-03 10:34 ` Florian Weimer
2020-11-03 10:26 ` [PATCH 4/4] aarch64: Remove the bti link_map field " Szabolcs Nagy
2020-11-03 17:34 ` [PATCH 0/4] aarch64: avoid mprotect(PROT_BTI|PROT_EXEC) " Mark Brown
2020-11-04 5:41 ` Jeremy Linton
2020-11-04 8:57 ` Szabolcs Nagy
2020-11-04 14:41 ` Catalin Marinas
2020-11-04 14:45 ` Florian Weimer [this message]
2020-11-04 10:50 ` Mark Brown
2020-11-04 18:47 ` Jeremy Linton
2020-11-04 18:53 ` Mark Brown
2020-11-04 9:02 ` Topi Miettinen
2020-11-04 9:20 ` Will Deacon
2020-11-04 9:29 ` Florian Weimer
2020-11-04 9:55 ` Topi Miettinen
2020-11-04 14:35 ` Catalin Marinas
2020-11-04 15:19 ` Topi Miettinen
2020-11-04 16:08 ` Szabolcs Nagy
2020-11-04 15:20 ` Mark Rutland
2020-11-04 18:59 ` Jeremy Linton
2020-11-05 11:31 ` Szabolcs Nagy
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=87ft5p2naf.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=broonie@kernel.org \
--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=mzxreary@0pointer.de \
--cc=s.mesoraca16@gmail.com \
--cc=szabolcs.nagy@arm.com \
--cc=toiwoton@gmail.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