public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH 3.19 v2 2/3] x86, mpx: Short-circuit the instruction decoder for unexpected opcodes
Date: Mon, 12 Jan 2015 15:47:16 -0800	[thread overview]
Message-ID: <54B45D04.2030309@linux.intel.com> (raw)
In-Reply-To: <6cb492e6037780a61b973cc9e40050d43452ed63.1421103159.git.luto@amacapital.net>

Couple of typos...

On 01/12/2015 03:04 PM, Andy Lutomirski wrote:
> +	/*
> +	 * We only _really_ need to decode bndcl/bndcn/bndcu
> +	 * Error out on anything else.  Check this before decoding the
> +	 * instruction to reduce our exposure to intentionally bad code
> +	 * to some extent.  Note that this shortcut cat incorrectly return

"...can incorrectly return"

> +	 * -EINVAL instead of -EFAULT under some circumstances.  This
> +	 * discrepency has no effect.
> +	 */

	^^ discrepancy


> +	if (nr_copied < 2)
> +		goto bad_opcode;
> +	if (buf[0] != 0x0f)
> +		goto bad_opcode;
> +	if (buf[1] != 0x1a && buf[1] != 0x1b)
> +		goto bad_opcode;
...
> -	/*
> -	 * We only _really_ need to decode bndcl/bndcn/bndcu
> -	 * Error out on anything else.
> -	 */
> -	if (insn->opcode.bytes[0] != 0x0f)
> -		goto bad_opcode;
> -	if ((insn->opcode.bytes[1] != 0x1a) &&
> -	    (insn->opcode.bytes[1] != 0x1b))
> -		goto bad_opcode;

Otherwise, this looks OK to me.  Have you tested this at all?  I know
you don't have any MPX hardware, but you can still hack something in to
point the instruction decoder at an MPX binary.

  reply	other threads:[~2015-01-12 23:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 23:04 [PATCH 3.19 v2 0/3] x86, mpx: Instruction decoder fixes and hardening Andy Lutomirski
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 [this message]
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=54B45D04.2030309@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --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