mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"alan@linux.intel.com" <alan@linux.intel.com>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"Reshetova, Elena" <elena.reshetova@intel.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"luto@kernel.org" <luto@kernel.org>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [GIT PULL] spectre variant1 mitigations for 4.16
Date: Wed, 24 Jan 2018 15:47:11 +0100	[thread overview]
Message-ID: <5fffd4e8-90fe-0799-adf0-5376113b268d@suse.cz> (raw)
In-Reply-To: <1516473386.30886.35.camel@intel.com>

On 01/20/2018, 07:36 PM, Williams, Dan J wrote:
> Dan Williams (9):
>       asm/nospec, array_ptr: sanitize speculative array de-references
>       x86: implement array_ptr_mask()
>       x86: introduce __uaccess_begin_nospec and ifence
>       x86, __get_user: use __uaccess_begin_nospec
>       x86, get_user: use pointer masking to limit speculation
>       x86: narrow out of bounds syscalls to sys_read under speculation
>       vfs, fdtable: prevent bounds-check bypass via speculative execution
>       kvm, x86: update spectre-v1 mitigation
>       nl80211: sanitize array index in parse_txq_params
> 
> Mark Rutland (1):
>       Documentation: document array_ptr
> 
>  Documentation/speculation.txt     | 143 ++++++++++++++++++++++++++++++++++++++
>  arch/x86/entry/entry_64.S         |   2 +
>  arch/x86/include/asm/barrier.h    |  28 ++++++++
>  arch/x86/include/asm/msr.h        |   3 +-
>  arch/x86/include/asm/smap.h       |  24 +++++++
>  arch/x86/include/asm/uaccess.h    |  15 +++-
>  arch/x86/include/asm/uaccess_32.h |   6 +-
>  arch/x86/include/asm/uaccess_64.h |  12 ++--
>  arch/x86/kvm/vmx.c                |  19 ++---
>  arch/x86/lib/getuser.S            |   5 ++
>  arch/x86/lib/usercopy_32.c        |   8 +--
>  include/linux/fdtable.h           |   7 +-
>  include/linux/nospec.h            |  65 +++++++++++++++++
>  net/wireless/nl80211.c            |  10 ++-

Could you update also cpu_show_spectre_v1?

thanks,
-- 
js
suse labs

      parent reply	other threads:[~2018-01-24 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20 18:36 Williams, Dan J
2018-01-20 19:49 ` Thomas Gleixner
2018-01-24 14:47 ` Jiri Slaby [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=5fffd4e8-90fe-0799-adf0-5376113b268d@suse.cz \
    --to=jslaby@suse.cz \
    --cc=alan@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=elena.reshetova@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®