public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Feng Liu <Feng.Liu3@windriver.com>
Cc: adobriyan@gmail.com, kees@kernel.org, sashal@kernel.org,
	Zhe.He@windriver.com, stable@vger.kernel.org
Subject: Re: [PATCH 5.10.y/5.15.y] ELF: fix kernel.randomize_va_space double read
Date: Tue, 20 May 2025 13:25:41 +0200	[thread overview]
Message-ID: <2025052021-freebee-clever-8fef@gregkh> (raw)
In-Reply-To: <20250509061415.435740-1-Feng.Liu3@windriver.com>

On Fri, May 09, 2025 at 02:14:15PM +0800, Feng Liu wrote:
> From: Alexey Dobriyan <adobriyan@gmail.com>
> 
> [ Upstream commit 2a97388a807b6ab5538aa8f8537b2463c6988bd2 ]
> 
> ELF loader uses "randomize_va_space" twice. It is sysctl and can change
> at any moment, so 2 loads could see 2 different values in theory with
> unpredictable consequences.
> 
> Issue exactly one load for consistent value across one exec.
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> Link: https://lore.kernel.org/r/3329905c-7eb8-400a-8f0a-d87cff979b5b@p183
> Signed-off-by: Kees Cook <kees@kernel.org>
> Signed-off-by: Feng Liu <Feng.Liu3@windriver.com>
> Signed-off-by: He Zhe <Zhe.He@windriver.com>
> ---
> Verified the build test.

No you did not!  This breaks the build.

This is really really annoying as it breaks the workflow on our side
when you submit code that does not work at all.

Please go and retest all of the outstanding commits that you all have
submitted and fix them up and resend them.  I'm dropping all of the rest
of them from my pending queue as this shows a total lack of testing
happening which implies that I can't trust any of these at all.

And I want you all to prove that you have actually tested the code, not
just this bland "Verified the build test" which is a _very_ low bar,
that is not even happening here at all :(

greg k-h

  parent reply	other threads:[~2025-05-20 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09  6:14 [PATCH 5.10.y/5.15.y] ELF: fix kernel.randomize_va_space double read Feng Liu
2025-05-12 18:04 ` Sasha Levin
2025-05-20 11:25 ` Greg KH [this message]
2025-05-22  7:40   ` He Zhe
2025-05-22  7:44     ` He Zhe
2025-05-22  8:36     ` Greg KH
2025-05-22  9:26       ` He Zhe
2025-05-22  9:40         ` Greg KH

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=2025052021-freebee-clever-8fef@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Feng.Liu3@windriver.com \
    --cc=Zhe.He@windriver.com \
    --cc=adobriyan@gmail.com \
    --cc=kees@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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