From: "Arnd Bergmann" <arnd@arndb.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Matt Turner" <mattst88@gmail.com>, "Kees Cook" <kees@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-alpha@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, "Michael Cree" <mcree@orcon.net.nz>,
"Sam James" <sam@gentoo.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Michael Karcher" <kernel@mkarcher.dialup.fu-berlin.de>,
"Chris Hofstaedtler" <zeha@debian.org>,
util-linux@vger.kernel.org, linux-mips@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH] alpha/elf: Fix misc/setarch test of util-linux by removing 32bit support
Date: Sat, 11 Jan 2025 12:26:18 +0100 [thread overview]
Message-ID: <6c1f31be-cd3b-4090-abbd-fd3968858e1b@app.fastmail.com> (raw)
In-Reply-To: <87jzb2tdb7.fsf_-_@email.froward.int.ebiederm.org>
On Sat, Jan 11, 2025, at 01:16, Eric W. Biederman wrote:
> Richard Henderson <richard.henderson@linaro.org> writes[1]:
>
>> There was a Spec benchmark (I forget which) which was memory bound and ran
>> twice as fast with 32-bit pointers.
>>
>> I copied the idea from DEC to the ELF abi, but never did all the other work
>> to allow the toolchain to take advantage.
>>
>> Amusingly, a later Spec changed the benchmark data sets to not fit into a
>> 32-bit address space, specifically because of this.
>>
>> I expect one could delete the ELF bit and personality and no one would
>> notice. Not even the 10 remaining Alpha users.
>
> In [2] it was pointed out that parts of setarch weren't working
> properly on alpha because it has it's own SET_PERSONALITY
> implementation. In the discussion that followed Richard Henderson
> pointed out that the 32bit pointer support for alpha was never
> completed.
>
> Fix this by removing alpha's 32bit pointer support.
>
> As a bit of paranoia refuse to execute any alpha binaries that hafe
> the EF_ALPHA_32BIT flag set. Just to fail explicitly in case someone
> somewhere has binaries that trying to use alpha's 32bit pointer
> support.
>
> [1]
> https://lkml.kernel.org/r/CAFXwXrkgu=4Qn-v1PjnOR4SG0oUb9LSa0g6QXpBq4ttm52pJOQ@mail.gmail.com
> [2]
> https://lkml.kernel.org/r/20250103140148.370368-1-glaubitz@physik.fu-berlin.de
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2025-01-11 11:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 14:01 [PATCH] alpha: Fix personality flag propagation across an exec John Paul Adrian Glaubitz
2025-01-08 22:49 ` Kees Cook
2025-01-09 0:52 ` Jeff Xu
2025-01-09 8:01 ` Arnd Bergmann
2025-01-09 8:43 ` Arnd Bergmann
2025-01-09 8:46 ` John Paul Adrian Glaubitz
2025-01-09 8:56 ` Arnd Bergmann
2025-01-09 9:12 ` John Paul Adrian Glaubitz
2025-01-09 16:18 ` Eric W. Biederman
2025-01-09 16:52 ` Arnd Bergmann
2025-01-09 17:17 ` Eric W. Biederman
2025-01-09 20:10 ` Maciej W. Rozycki
2025-01-09 20:53 ` Arnd Bergmann
2025-01-12 14:40 ` Maciej W. Rozycki
2025-01-10 0:28 ` Richard Henderson
2025-01-11 0:16 ` [PATCH] alpha/elf: Fix misc/setarch test of util-linux by removing 32bit support Eric W. Biederman
2025-01-11 1:17 ` Richard Henderson
2025-01-11 10:37 ` John Paul Adrian Glaubitz
2025-01-12 14:40 ` Maciej W. Rozycki
2025-01-12 14:56 ` John Paul Adrian Glaubitz
2025-01-13 5:39 ` [PATCH v2] " Eric W. Biederman
2025-01-18 10:35 ` Ivan Kokshaysky
2025-01-26 17:15 ` John Paul Adrian Glaubitz
2025-01-27 13:27 ` Ivan Kokshaysky
2025-02-03 11:55 ` John Paul Adrian Glaubitz
2025-02-06 15:42 ` Kees Cook
2025-01-11 11:26 ` Arnd Bergmann [this message]
2025-01-11 15:27 ` [PATCH] " Ivan Kokshaysky
2025-01-13 5:32 ` Eric W. Biederman
2025-01-11 21:26 ` John Paul Adrian Glaubitz
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=6c1f31be-cd3b-4090-abbd-fd3968858e1b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kees@kernel.org \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=loongarch@lists.linux.dev \
--cc=macro@orcam.me.uk \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=paulmck@kernel.org \
--cc=richard.henderson@linaro.org \
--cc=sam@gentoo.org \
--cc=util-linux@vger.kernel.org \
--cc=zeha@debian.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