All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Updated L1TF native OS patch
Date: Thu, 3 May 2018 12:04:06 +0200	[thread overview]
Message-ID: <20180503100406.GF4535@dhcp22.suse.cz> (raw)
In-Reply-To: <20180502121420.GB31258@dhcp22.suse.cz>

On Wed 02-05-18 14:14:20, speck for Michal Hocko wrote:
[...]
> I have to confess that I do not understand the thread model for
> PROT_NONE patch though. The mitigation _has_ to be done on the
> VM layer otherwise we are screwed. So why should we even bother
> and make the code even more kludgy?

Now with the thread model clarified and the patch reviewed you can add
Acked-by: Michal Hocko <mhocko@suse.com>

I still think that the changelog could be more explicit but leave the
decision on you.

-- 
Michal Hocko
SUSE Labs

      parent reply	other threads:[~2018-05-03 10:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 23:42 [MODERATED] Updated L1TF native OS patch Andi Kleen
2018-05-01 23:59 ` [MODERATED] " Linus Torvalds
2018-05-02  0:05   ` Andi Kleen
2018-05-02  1:21     ` Andi Kleen
2018-05-02  8:04       ` Peter Zijlstra
2018-05-02 10:48       ` Thomas Gleixner
2018-05-02 12:04         ` Thomas Gleixner
2018-05-02 14:50         ` [MODERATED] " Andi Kleen
2018-05-02 14:53           ` Thomas Gleixner
2018-05-02 12:14       ` [MODERATED] " Michal Hocko
2018-05-02 12:36         ` Thomas Gleixner
2018-05-02 12:44           ` [MODERATED] " Michal Hocko
2018-05-02 15:07         ` Andi Kleen
2018-05-02 15:35           ` Michal Hocko
2018-05-02 16:08             ` Andi Kleen
2018-05-03  9:26               ` Michal Hocko
2018-05-03 10:04         ` Michal Hocko [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=20180503100406.GF4535@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=speck@linutronix.de \
    /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.