From: Sean Christopherson <seanjc@google.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Sean Christopherson <seanjc@google.com>,
Dmitry Vyukov <dvyukov@google.com>
Subject: [PATCH 0/2] x86/mm: More KASAN per-CPU CEA mapping bug fixes
Date: Fri, 4 Nov 2022 22:00:51 +0000 [thread overview]
Message-ID: <20221104220053.1702977-1-seanjc@google.com> (raw)
Two more bug fixes from the gift that keeps on giving. Both of these were
found by inspection, and both are lightly tested. I'm pretty confident
that patch 01 fixes a real bug, somewhat less so about patch 02, though
given the other issues I debugged I don't see anything that prevents the
DS buffers from exploding.
Sean Christopherson (2):
x86/mm: Recompute physical address for every page of per-CPU CEA
mapping
x86/mm: Populate KASAN shadow for per-CPU DS buffers in CPU entry area
arch/x86/mm/cpu_entry_area.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
base-commit: 3301badde43dee7c2a013fbd6479c258366519da
--
2.38.1.431.g37b22c650d-goog
next reply other threads:[~2022-11-04 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 22:00 Sean Christopherson [this message]
2022-11-04 22:00 ` [PATCH 1/2] x86/mm: Recompute physical address for every page of per-CPU CEA mapping Sean Christopherson
2022-11-04 22:00 ` [PATCH 2/2] x86/mm: Populate KASAN shadow for per-CPU DS buffers in CPU entry area Sean Christopherson
2022-11-09 17:50 ` Sean Christopherson
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=20221104220053.1702977-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=ryabinin.a.a@gmail.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 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.