Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	Eric Biggers <ebiggers@kernel.org>,
	Kyle Zeng <kylebot@openai.com>,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] KEYS: changes for v7.4-rc1
Date: Thu, 22 Oct 2026 23:53:06 +0300	[thread overview]
Message-ID: <atp3sgtYEQ1z0Dd4@kernel.org> (raw)
In-Reply-To: <CAHk-=wjouh66VCZjhUedb+wkRTWB0vsoDjU3N0huGsiYXQ5S0A@mail.gmail.com>

On Thu, Oct 22, 2026 at 10:06:56AM -1000, Linus Torvalds wrote:
> On Wed, 21 Oct 2026 at 04:22, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > A patch that Kyle Zeng submitted addresses a critical bug [..]
> 
> Note that breaking local KASLR is not a "critical bug". We just call
> it "Thursday".
> 
> Breaking KASRL locally is trivial using just all the normal local CPU
> timing attacks.
> 
> KASLR is there to make remote attacks harder.
> 
>                Linus

Ok, that's fair and makes sense.

Br, Jarkko

  reply	other threads:[~2026-10-22 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 14:22 [GIT PULL] KEYS: changes for v7.4-rc1 Jarkko Sakkinen
2026-10-22 20:06 ` Linus Torvalds
2026-10-22 20:53   ` Jarkko Sakkinen [this message]
2026-10-22 20:50 ` pr-tracker-bot

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=atp3sgtYEQ1z0Dd4@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=kylebot@openai.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zohar@linux.ibm.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