mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: s1nkhole <dedemorow@gmail.com>
To: dave.hansen@intel.com
Cc: x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	hpa@zytor.com, Peter Zijlstra <peterz@infradead.org>,
	Kees Cook <kees@kernel.org>, Brian Gerst <brgerst@gmail.com>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrey Zakharov <dedemorow@gmail.com>
Subject: Re: [PATCH] x86/entry/32: Harden return-to-user
Date: Wed, 28 Oct 2026 22:21:39 +0300	[thread overview]
Message-ID: <20261028192139.32606-1-dedemorow@gmail.com> (raw)
In-Reply-To: <ac147f25-a2d3-46b9-89c5-44a1c0e4f038@intel.com>

From: Andrey Zakharov <dedemorow@gmail.com>

On 10/27/26 15:01, Dave Hansen wrote:
> I'm curious who cares.
>
> Is anyone who is actually still running a 32-bit kernel concerned about
> this kind of hardening?
>
> If no one cares, then I'd rather pass on the complexity, even four
> instructions of it.

I don't know of anyone. The only motivation was KSPP issue #41, which
asks for parity with the x86-64 check added by 1e4d3001f59f, and that
issue is marked as low priority because 32-bit is legacy. I have no
report from a 32-bit user asking for it.

Please drop the patch. Thanks for looking at it.

If you have a moment: this is my first work on arch/x86, and I would like
to contribute something that is actually useful. Is there a small task
in x86/entry or in kernel hardening that you would suggest as a better
starting point, or a place where help with testing or review would be
welcome? I can build and run kernels under QEMU.

Thanks,
Andrey Zakharov

  reply	other threads:[~2026-10-28 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 21:52 Andrey Zakharov
2026-10-27 22:01 ` Dave Hansen
2026-10-28 19:21   ` s1nkhole [this message]
2026-10-28 20:40     ` Borislav Petkov
2026-10-28 20:50     ` Dave Hansen

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=20261028192139.32606-1-dedemorow@gmail.com \
    --to=dedemorow@gmail.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --cc=x86@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®