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 v2 0/3] x86, mpx: Instruction decoder fixes and hardening
Date: Mon, 12 Jan 2015 15:04:08 -0800 [thread overview]
Message-ID: <cover.1421103159.git.luto@amacapital.net> (raw)
Hi all-
Sorry, this is later than I had hoped to send this. This series has
three minor fixes for mpx and the instruction decoder.
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 (3):
x86: Fix off-by-one in the instruction decoder length checks
x86, mpx: Short-circuit the instruction decoder for unexpected opcodes
x86: Enforce MAX_INSN_SIZE in the instruction decoder
arch/x86/lib/insn.c | 9 ++++++++-
arch/x86/mm/mpx.c | 25 ++++++++++++++++---------
2 files changed, 24 insertions(+), 10 deletions(-)
--
2.1.0
next reply other threads:[~2015-01-12 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 23:04 Andy Lutomirski [this message]
2015-01-12 23:04 ` [PATCH 3.19 v2 1/3] x86: Fix off-by-one in the instruction decoder length checks Andy Lutomirski
2015-01-12 23:13 ` Dave Hansen
2015-01-12 23:18 ` Andy Lutomirski
2015-01-12 23:04 ` [PATCH 3.19 v2 2/3] x86, mpx: Short-circuit the instruction decoder for unexpected opcodes Andy Lutomirski
2015-01-12 23:47 ` Dave Hansen
2015-01-12 23:57 ` Andy Lutomirski
2015-01-14 19:43 ` Dave Hansen
2015-01-14 20:24 ` Andy Lutomirski
2015-01-12 23:04 ` [PATCH 3.19 v2 3/3] x86: Enforce MAX_INSN_SIZE in the instruction decoder Andy Lutomirski
2015-01-13 12:20 ` Masami Hiramatsu
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.1421103159.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox