mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] x86: Fix and enforce max instruction size in the insn decoder
Date: Wed, 28 Jan 2015 12:12:15 +0900	[thread overview]
Message-ID: <54C8538F.7010103@hitachi.com> (raw)
In-Reply-To: <f8f0bc9b8c58cfd6830f7d88400bf1396cbdcd0f.1422403511.git.luto@amacapital.net>

(2015/01/28 9:06), Andy Lutomirski wrote:
> x86 instructions cannot exceed 15 bytes, and the instruction decoder
> should enforce that.  Prior to 6ba48ff46f76, the instruction length
> limit was implicitly set to 16, which was an approximation of 15,
> but there is currently no limit at all.
> 
> Fix MAX_INSN_SIZE (it should be 15, not 16), and fix the decoder to
> reject instructions that exceed MAX_INSN_SIZE.
> 
> Other than potentially confusing some of the decoder sanity checks,
> I'm not aware of any actual problems that omitting this check would
> cause, nor am I aware of any practical problems caused by the
> MAX_INSN_SIZE error.
> 

Thank you for updating. This looks good to me :)

Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>

Ingo, could you pull this in -tip tree?

Thank you,

> Fixes: 6ba48ff46f76 x86: Remove arbitrary instruction size limit in instruction decoder
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> ---
> 
> Changes from old versions: folded
> 
> arch/x86/include/asm/insn.h | 2 +-
>  arch/x86/lib/insn.c         | 7 +++++++
>  2 files changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/include/asm/insn.h b/arch/x86/include/asm/insn.h
> index 47f29b1d1846..e7814b74caf8 100644
> --- a/arch/x86/include/asm/insn.h
> +++ b/arch/x86/include/asm/insn.h
> @@ -69,7 +69,7 @@ struct insn {
>  	const insn_byte_t *next_byte;
>  };
>  
> -#define MAX_INSN_SIZE	16
> +#define MAX_INSN_SIZE	15
>  
>  #define X86_MODRM_MOD(modrm) (((modrm) & 0xc0) >> 6)
>  #define X86_MODRM_REG(modrm) (((modrm) & 0x38) >> 3)
> diff --git a/arch/x86/lib/insn.c b/arch/x86/lib/insn.c
> index 2480978b31cc..bf1f227cf706 100644
> --- a/arch/x86/lib/insn.c
> +++ b/arch/x86/lib/insn.c
> @@ -52,6 +52,13 @@
>   */
>  void insn_init(struct insn *insn, const void *kaddr, int buf_len, int x86_64)
>  {
> +	/*
> +	 * Instructions longer than MAX_INSN_SIZE (15 bytes) are invalid
> +	 * even if the input buffer is long enough to hold them.
> +	 */
> +	if (buf_len > MAX_INSN_SIZE)
> +		buf_len = MAX_INSN_SIZE;
> +
>  	memset(insn, 0, sizeof(*insn));
>  	insn->kaddr = kaddr;
>  	insn->end_kaddr = kaddr + buf_len;
> 


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



  reply	other threads:[~2015-01-28  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  0:06 Andy Lutomirski
2015-01-28  3:12 ` Masami Hiramatsu [this message]
2015-02-19  0:28 ` [tip:x86/asm] x86/asm/decoder: " tip-bot for 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=54C8538F.7010103@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@elte.hu \
    --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

Powered by JetHome