From: Kees Cook <kees@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tip-commits@vger.kernel.org,
Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org
Subject: Re: hardened_usercopy 32-bit (was: Re: [tip: x86/merge] x86/fpu: Make task_struct::thread constant size)
Date: Sun, 4 May 2025 15:43:07 -0700 [thread overview]
Message-ID: <202505041541.C3D97BE@keescook> (raw)
In-Reply-To: <202505041418.F47130C4C8@keescook>
On Sun, May 04, 2025 at 03:30:38PM -0700, Kees Cook wrote:
> However, I can't test this patch -- I'm not able to reproduce the problem
> either, even with your .config. What hardware are you using?
Oh, wait, yes, I reproduced it. I just didn't actually log in or wait for
complex daemons to start. Without my patch I quickly see the crashes. With
my patch, everything is fine. So, I can confirm that fixes it.
--
Kees Cook
next prev parent reply other threads:[~2025-05-04 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 12:07 hardened_usercopy 32-bit (was: Re: [tip: x86/merge] x86/fpu: Make task_struct::thread constant size) Borislav Petkov
2025-05-04 6:45 ` Ingo Molnar
2025-05-04 8:44 ` Ingo Molnar
2025-05-04 9:50 ` Borislav Petkov
2025-05-04 9:53 ` Ingo Molnar
2025-05-04 22:30 ` Kees Cook
2025-05-04 22:43 ` Kees Cook [this message]
2025-05-05 9:15 ` Borislav Petkov
2025-05-05 11:31 ` Ingo Molnar
2025-05-05 21:09 ` Kees Cook
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=202505041541.C3D97BE@keescook \
--to=kees@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=chang.seok.bae@intel.com \
--cc=gustavoars@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.