All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: x86@kernel.org, linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 3.19 v4 0/2] x86, mpx: Instruction decoder fixes and hardening
Date: Tue, 13 Jan 2015 13:49:18 -0800	[thread overview]
Message-ID: <cover.1421183147.git.luto@amacapital.net> (raw)

Hi all-

Ingo and Thomas, I think this is in decent shape for x86/urgent now
if you think it's appropriate to apply at this point in the cycle.

Changes from v3:
 - Replaced MAX_INSN_SIZE with 15 in the decoder change.  (Masami)
   I'll send the patch for 3.20 to fix MAX_INSN_SIZE separately.

Changes from v2:
 - Dropped patch 1 (fixed in tip separately)
 - Fixed comment typoes in patch 2 (noticed by Dave)

Changes from v1:
 - Dropped the TIF_IA32 change -- let's defer that until at least 3.20.
 - Fixed the MPX decode short-circuit.  v1 was buggy.
 - Patch 3 is new.  It fixes a minor regression from the MPX work.

Andy Lutomirski (2):
  x86, mpx: Short-circuit the instruction decoder for unexpected opcodes
  x86: Enforce maximum instruction size in the instruction decoder

 arch/x86/lib/insn.c |  7 +++++++
 arch/x86/mm/mpx.c   | 25 ++++++++++++++++---------
 2 files changed, 23 insertions(+), 9 deletions(-)

-- 
2.1.0


             reply	other threads:[~2015-01-13 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 21:49 Andy Lutomirski [this message]
2015-01-13 21:49 ` [PATCH 3.19 v4 1/2] x86, mpx: Short-circuit the instruction decoder for unexpected opcodes Andy Lutomirski
2015-01-20 13:59   ` Thomas Gleixner
2015-01-20 22:28     ` Andy Lutomirski
2015-01-13 21:49 ` [PATCH 3.19 v4 2/2] x86: Enforce maximum instruction size in the instruction decoder Andy Lutomirski
2015-01-15 12:37   ` Masami Hiramatsu
2015-01-15 15:22     ` Andy Lutomirski
2015-01-16  1:02       ` Masami Hiramatsu
2015-01-27 23:56         ` Andy Lutomirski

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=cover.1421183147.git.luto@amacapital.net \
    --to=luto@amacapital.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.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 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.