From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: Siarhei.Liakh@concurrent-rt.com,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bpetkov@suse.de>
Subject: Re: [PATCH] x86: Call fixup_exception() before notify_die() in math_error()
Date: Tue, 19 Jun 2018 08:23:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1806190820210.1692@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CALCETrXUdLZTnf0EF2LVM4ru2G6nkFX--gQ=6JpBRNZ7Gm+MsQ@mail.gmail.com>
On Mon, 18 Jun 2018, Andy Lutomirski wrote:
> On Thu, Jun 14, 2018 at 10:10 PM Siarhei Liakh
> <Siarhei.Liakh@concurrent-rt.com> wrote:
> >
> > fpu__drop() has an explicit fwait which under some conditions can trigger
> > a fixable FPU exception while in kernel. Thus, we should attempt to fixup
> > the exception first, and only call notify_die() if the fixup failed just
> > like in do_general_protection(). The original call sequence incorrectly
> > triggers KDB entry on debug kernels under particular FPU-intensive
> > workloads. This issue had been privately observed, fixed, and tested
> > on 4.9.98, while this patch brings the fix to the upstream.
>
> Reviewed-by: Andy Lutomirski <luto@kernel.org>
>
> With the caveat that you are perpetuating what is arguably a bug in
> some of the other entries: math_error() can now be called with IRQs
> off and return with IRQs on. If we actually start asserting good
> behavior in the entry code, we'll need to fix this.
Confused. math_error() is still invoked with interrupts off. What's
different now is that notify_die() is called with interrupts conditionally
enabled while upstream it's always called with interrupts disabled.
Thanks,
tglx
next prev parent reply other threads:[~2018-06-19 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 19:36 Siarhei Liakh
2018-06-18 21:47 ` Andy Lutomirski
2018-06-19 6:23 ` Thomas Gleixner [this message]
2018-06-19 15:23 ` Andy Lutomirski
[not found] ` <DM5PR11MB2011397361BB5C0FB3D4FDFFB1700@DM5PR11MB2011.namprd11.prod.outlook.com>
[not found] ` <B739D98B-BA3F-40F6-82DF-6444546B6B4C@amacapital.net>
2018-06-19 19:56 ` Siarhei Liakh
2018-06-20 9:48 ` [tip:x86/urgent] " tip-bot for Siarhei Liakh
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=alpine.DEB.2.21.1806190820210.1692@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Siarhei.Liakh@concurrent-rt.com \
--cc=bpetkov@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®