[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210608143617.565868844@linutronix.de>
Date: Tue, 08 Jun 2021 16:36:17 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: LKML <linux-kernel@...r.kernel.org>
Cc: x86@...nel.org, Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Tony Luck <tony.luck@...el.com>,
Yu-cheng Yu <yu-cheng.yu@...el.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Borislav Petkov <bp@...e.de>, Rik van Riel <riel@...riel.com>
Subject: [patch V3 0/6] x86/fpu: Mop up XSAVES and related damage
syszbot reported a warnon for XRSTOR raising #GP:
https://lore.kernel.org/r/0000000000004c453905c30f8334@google.com
with a syzcaller reproducer and a conclusive bisect result. It took a
while to destill a simple C reproducer out of it which allowed to pin point
the root cause: The recent addition of supervisor XSTATEs broke the signal
restore path for the case where the signal handler wreckaged the XSTATE on
stack because it does not sanitize the XSTATE header which causes a
subsequent XRSTOR to fail and #GP.
The following series addresses the problem and fixes related issues
which were found while inspecting the related changes and testing
signal restore and PKRU.
V2 of this can be found here:
https://lore.kernel.org/r/20210605234742.712464974@linutronix.de
Changes vs. V2:
- Drop the cleanup patches for now, so the bug fixes make progress
- Fix the PKRU context switch code
- Address review comments
Thanks,
tglx
Powered by blists - more mailing lists