From: Eric Biggers <ebiggers@kernel.org>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org
Cc: Alexander Potapenko <glider@google.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: suppress KMSAN reports in arch_within_stack_frames()
Date: Fri, 27 Jan 2023 08:12:03 -0800 [thread overview]
Message-ID: <Y9P301c/cQ/wLTMs@sol.localdomain> (raw)
In-Reply-To: <Y7+dXStDx9G0h2JE@sol.localdomain>
On Wed, Jan 11, 2023 at 09:40:47PM -0800, Eric Biggers wrote:
> On Tue, Nov 29, 2022 at 09:40:45PM -0800, Eric Biggers wrote:
> > On Fri, Nov 18, 2022 at 06:23:05PM +0100, Alexander Potapenko wrote:
> > > arch_within_stack_frames() performs stack walking and may confuse
> > > KMSAN by stepping on stale shadow values. To prevent false positive
> > > reports, disable KMSAN checks in this function.
> > >
> > > This fixes KMSAN's interoperability with CONFIG_HARDENED_USERCOPY.
> > >
> > > Link: https://github.com/google/kmsan/issues/89
> > > Link: https://lore.kernel.org/lkml/Y3b9AAEKp2Vr3e6O@sol.localdomain/
> > > Cc: Eric Biggers <ebiggers@kernel.org>
> > > Signed-off-by: Alexander Potapenko <glider@google.com>
> > > ---
> > > arch/x86/include/asm/thread_info.h | 5 +++++
> > > 1 file changed, 5 insertions(+)
> >
> > Tested-by: Eric Biggers <ebiggers@google.com>
> >
>
> Can this patch be applied to the x86 tree, please?
>
> - Eric
Ping.
prev parent reply other threads:[~2023-01-27 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 17:23 [PATCH] x86: suppress KMSAN reports in arch_within_stack_frames() Alexander Potapenko
2022-11-21 10:22 ` Peter Zijlstra
2022-11-21 10:28 ` Alexander Potapenko
2022-11-21 11:38 ` Peter Zijlstra
2022-11-21 14:27 ` Alexander Potapenko
2022-11-22 8:17 ` Peter Zijlstra
2022-11-30 5:40 ` Eric Biggers
2023-01-12 5:40 ` Eric Biggers
2023-01-27 16:12 ` Eric Biggers [this message]
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=Y9P301c/cQ/wLTMs@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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