From: Yves-Alexis Perez <corsac@debian.org>
To: Yang Shi <shy828301@gmail.com>,
jirislaby@kernel.org, surenb@google.com, riel@surriel.com,
willy@infradead.org, cl@linux.com, akpm@linux-foundation.org
Cc: yang@os.amperecomputing.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Salvatore Bonaccorso <carnil@debian.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH] mm: huge_memory: don't force huge page alignment on 32 bit
Date: Thu, 11 Jul 2024 22:10:12 +0200 [thread overview]
Message-ID: <2d7bd8b2b9736d4a7d0a26169978372b5e002a62.camel@debian.org> (raw)
In-Reply-To: <20240118133504.2910955-1-shy828301@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Thu, 2024-01-18 at 05:35 -0800, Yang Shi wrote:
> The commit efa7df3e3bb5 ("mm: align larger anonymous mappings on THP
> boundaries") caused two issues [1] [2] reported on 32 bit system or compat
> userspace.
>
> It doesn't make too much sense to force huge page alignment on 32 bit
> system due to the constrained virtual address space.
Hi people,
sorry for beeing so late. I've looked at this following the OpenSSH issue
(CVE-2024-6387 [1]) and especially the impact on IA-32 installations where
ASLR is apparently broken.
There was a recent thread [2] on oss-security discussing the issue.
Looking at the commit log I think the intention was to fix this both for:
- - 32 bit process running on 64 bit kernels: in_compat_syscall()
- - all processes running on 32 bit kernels: IS_ENABLED(CONFIG_32BIT)
Unfortunately, as far as I can tell, CONFIG_32BIT is not enabled on 32bit x86
kernels. Maybe CONFIG_X86_32 would be the right one there?
[1] https://www.openwall.com/lists/oss-security/2024/07/01/3
[2] https://www.openwall.com/lists/oss-security/2024/07/08/3
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmaQPCQACgkQ3rYcyPpX
RFvSHQf/VE7td7scTTsrK7Cx0F3MmDLFgjUDbMDuyPq6lNQqnDbd2zc00JP1eeLs
/mW1uZNbR92bn6xq2sPJu7c6tB3MJuiQme+ZqnPfIgyoWc89i6V6WUXTZN077lIl
xJZxHLMei5KreHz66AYU66HdU89knMTcX362YyyI8dEZKXS3FlP0SLSoBM0UKY0G
HYM6+GetE+fINhfNSMpHgqkTQB825Vqdq5UBsBjHYMg5RJ92/fDgUo5RD7qm/HVz
SDDNSGwpVwYZ20RnnD+DOS9rsnyR4FcAP0m0dcTmQdM8GcY4SyjnEux5idvCicjy
a1jmvsSLxCMZ9mZsrsipIZoNhSHlDA==
=f0Lk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2024-07-11 20:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 13:35 Yang Shi
2024-01-18 18:05 ` Yang Shi
2024-01-19 0:16 ` Matthew Wilcox
2024-01-18 20:14 ` Matthew Wilcox
2024-01-18 20:39 ` Yang Shi
2024-01-19 17:16 ` Rik van Riel
2024-01-25 8:53 ` Michal Hocko
2024-01-26 9:36 ` Jiri Slaby
2024-01-26 9:41 ` Jiri Slaby
2024-01-26 10:51 ` Michal Hocko
2024-02-03 9:24 ` Thorsten Leemhuis
2024-02-05 17:07 ` Yang Shi
2024-02-05 17:53 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-12 13:45 ` Thorsten Leemhuis
2024-02-18 9:26 ` Greg KH
2024-07-11 20:10 ` Yves-Alexis Perez [this message]
2024-07-11 20:47 ` Yang Shi
2024-07-11 20:50 ` Matthew Wilcox
2024-07-11 20:53 ` Yang Shi
2024-07-12 14:41 ` Yves-Alexis Perez
2024-07-12 15:31 ` Yang Shi
2024-07-11 20:52 ` Ben Hutchings
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=2d7bd8b2b9736d4a7d0a26169978372b5e002a62.camel@debian.org \
--to=corsac@debian.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=cl@linux.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=shy828301@gmail.com \
--cc=surenb@google.com \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox