All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Andy Lutomirski <luto@kernel.org>
Cc: stable@vger.kernel.org, Matthew Whitehead <tedheadster@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	"H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH BACKPORT 3.4 - 4.5] x86/traps: Ignore high word of regs->cs in early_idt_handler_common
Date: Thu, 1 Dec 2016 15:51:24 +0100	[thread overview]
Message-ID: <20161201145124.GA17630@1wt.eu> (raw)
In-Reply-To: <e0022be5c4b69b8e5281ea0712a3059e89c0130f.1480538175.git.luto@kernel.org>

On Wed, Nov 30, 2016 at 12:37:53PM -0800, Andy Lutomirski wrote:
> This is a backport of:
> commit cb32c69920e58a1a58e7b5cad975038a69c0ce7d 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 commit 1e02ce4cccdc ("x86:
> Store a per-cpu shadow copy of CR4") and commit 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. ]

This morning before coffee took effect I read 3.4-3.5 so I classed
it, now I've queued it for 3.10.

Thanks Andy!
Willy

      parent reply	other threads:[~2016-12-01 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 20:37 [PATCH BACKPORT 3.4 - 4.5] x86/traps: Ignore high word of regs->cs in early_idt_handler_common Andy Lutomirski
2016-12-01  8:48 ` Jiri Slaby
2016-12-01 17:26   ` Andy Lutomirski
2016-12-01 14:51 ` Willy Tarreau [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=20161201145124.GA17630@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=luto@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tedheadster@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.