From: Stian Halseth <stian@itx.no>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Andreas Larsson <andreas@gaisler.com>,
"David S . Miller" <davem@davemloft.net>
Cc: Kees Cook <kees@kernel.org>,
Michel Lespinasse <michel@lespinasse.org>,
Jan Engelhardt <jengelh@inai.de>,
sparclinux@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] sparc64: Randomize mmap base and PIE executables
Date: Sun, 18 Oct 2026 15:33:34 +0200 [thread overview]
Message-ID: <6e2d2b2b7aa4029c261831016d8b6c40bc335341.camel@itx.no> (raw)
In-Reply-To: <e3068b5c97884032e7cbd12c78f6b5534d75e30c.camel@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Hi Adrian,
On Sun, 2026-10-18 at 15:09 +0200, John Paul Adrian Glaubitz wrote:
>
> What about sparc32? Does it use address base randomization at all?
>
sparc32 is at the same state as sparc64 was before this series. Only
the stack moves.
I've only tested 32-bit programs on sparc64. The same approach will
probably work, but needs testing on real sparc32. Could be possibly be
added as a follow up, if someone with sparc32 hardware can test it.
/Stian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-18 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 12:27 Stian Halseth
2026-10-18 12:27 ` [PATCH v2 1/3] sparc64: Start bottom-up mmap searches at mm->mmap_base Stian Halseth
2026-10-18 12:27 ` [PATCH v2 2/3] sparc64: Move the 32-bit PIE base below the legacy mmap base Stian Halseth
2026-10-18 12:27 ` [PATCH v2 3/3] sparc64: Randomize the load address of PIE executables Stian Halseth
2026-10-18 13:09 ` [PATCH v2 0/3] sparc64: Randomize mmap base and " John Paul Adrian Glaubitz
2026-10-18 13:33 ` Stian Halseth [this message]
2026-10-18 13:38 ` Stian Halseth
2026-10-18 20:37 ` Magnus Lindholm
2026-10-18 21:08 ` Stian Halseth
2026-10-18 21:12 ` Magnus Lindholm
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=6e2d2b2b7aa4029c261831016d8b6c40bc335341.camel@itx.no \
--to=stian@itx.no \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jengelh@inai.de \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michel@lespinasse.org \
--cc=sparclinux@vger.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
all inboxes | Powered by JetHome®