From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Kees Cook <kees@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, Oleg Nesterov <oleg@redhat.com>
Subject: Re: hardened_usercopy 32-bit (was: Re: [tip: x86/merge] x86/fpu: Make task_struct::thread constant size)
Date: Sun, 4 May 2025 11:53:24 +0200 [thread overview]
Message-ID: <aBc5FNmf-pl6iypR@gmail.com> (raw)
In-Reply-To: <20250504095041.GAaBc4cRpKHJvo5fRE@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> On Sun, May 04, 2025 at 10:44:20AM +0200, Ingo Molnar wrote:
> > > Thx for the report, mind sending the exact .config that fails for you?
> >
> > BTW., mind sending the full bootlog as well? I cannot reproduce it here
> > with CONFIG_HARDENED_USERCOPY=y, so I suspect it's something about the
> > build, HW or boot environment.
>
> Attaching boot.log and .config.
>
> Toolchain is:
>
> gcc (Debian 13.2.0-25) 13.2.0
Thanks!
Ingo
next prev parent reply other threads:[~2025-05-04 9:53 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 [this message]
2025-05-04 22:30 ` Kees Cook
2025-05-04 22:43 ` Kees Cook
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=aBc5FNmf-pl6iypR@gmail.com \
--to=mingo@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=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--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.