From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: stable@vger.kernel.org, Matthew Whitehead <tedheadster@gmail.com>,
Jiri Slaby <jslaby@suse.cz>, Willy Tarreau <w@1wt.eu>,
"H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH BACKPORT v2 3.4 - 4.5] x86/traps: Ignore high word of regs->cs in early_idt_handler_common
Date: Fri, 2 Dec 2016 18:07:26 +0100 [thread overview]
Message-ID: <20161202170726.GA7340@kroah.com> (raw)
In-Reply-To: <e0022be5c4b69b8e5281ea0712a3059e89c0130f.1480538176.git.luto@kernel.org>
On Thu, Dec 01, 2016 at 09:26:42AM -0800, Andy Lutomirski wrote:
> This is a backport of:
> commit fc0e81b2bea0ebceb71889b61d2240856141c9ee upstream
>
> On the 80486 DX, it seems that some exceptions may leave garbage in
> the high bits of CS. This causes sporadic failures in which
> early_fixup_exception() refuses to fix up an exception.
>
> As far as I can tell, this has been buggy for a long time, but the
> problem seems to have been exacerbated by commits:
>
> 1e02ce4cccdc ("x86: Store a per-cpu shadow copy of CR4")
> e1bfc11c5a6f ("x86/init: Fix cr4_init_shadow() on CR4-less machines")
>
> This appears to have broken for as long as we've had early
> exception handling.
>
> [ This backport should apply to kernels from 3.4 - 4.5. ]
Thanks for the backport, now queued up for 4.4-stable.
greg k-h
next prev parent reply other threads:[~2016-12-02 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 17:26 [PATCH BACKPORT v2 3.4 - 4.5] x86/traps: Ignore high word of regs->cs in early_idt_handler_common Andy Lutomirski
2016-12-02 17:07 ` Greg KH [this message]
2017-02-15 1:45 ` Ben Hutchings
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=20161202170726.GA7340@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=luto@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tedheadster@gmail.com \
--cc=w@1wt.eu \
/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;
as well as URLs for NNTP newsgroup(s).