From: Tim Chen <tim.c.chen@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: David Woodhouse <dwmw@amazon.co.uk>,
arjan@linux.intel.com, tglx@linutronix.de, karahmed@amazon.de,
x86@kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, pbonzini@redhat.com, ak@linux.intel.com,
torvalds@linux-foundation.org, gregkh@linux-foundation.org,
mingo@kernel.org, luto@kernel.org, linux@dominikbrodowski.net
Subject: Re: [PATCH] x86/speculation: Use Indirect Branch Prediction Barrier in context switch
Date: Tue, 30 Jan 2018 14:26:53 -0800 [thread overview]
Message-ID: <296de30b-515b-6eab-1b13-bb2f71451004@linux.intel.com> (raw)
In-Reply-To: <20180130215731.pszc5u4gcc32ds4v@pd.tnic>
On 01/30/2018 01:57 PM, Borislav Petkov wrote:
> On Tue, Jan 30, 2018 at 01:03:20PM -0800, Tim Chen wrote:
>> So it doesn't seem to be very practical attack if the victim has set
>> itself to be non-dumpable.
>
> Probably, but considering how cheap our fix is, we might just as well
> plug that hole too.
>
If the process has multiple threads running on different cpus,
you will need to set IBPB on all cpus they are running in
order to achieve your purpose. So it is not necessarily cheap.
But I don't think it is really necessary.
Tim
next prev parent reply other threads:[~2018-01-30 22:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 22:04 [PATCH] x86/speculation: Use Indirect Branch Prediction Barrier in context switch David Woodhouse
2018-01-30 17:48 ` Josh Poimboeuf
2018-01-30 21:23 ` Tim Chen
2018-01-30 22:00 ` Borislav Petkov
2018-01-30 22:21 ` Thomas Gleixner
2018-01-30 22:55 ` Borislav Petkov
2018-01-31 3:59 ` Josh Poimboeuf
2018-01-31 23:25 ` Tim Chen
2018-01-30 20:38 ` Borislav Petkov
2018-01-30 21:03 ` Tim Chen
2018-01-30 21:57 ` Borislav Petkov
2018-01-30 22:26 ` Tim Chen [this message]
2018-01-30 22:43 ` Borislav Petkov
2018-01-31 0:25 ` Tim Chen
2018-01-31 0:41 ` Borislav Petkov
2018-01-30 22:39 ` [tip:x86/pti] " tip-bot for Tim Chen
2018-01-31 7:03 ` Dominik Brodowski
2018-01-31 13:24 ` Josh Poimboeuf
2018-02-01 8:25 ` Christian Brauner
2018-02-01 8:31 ` David Woodhouse
2018-02-01 15:40 ` Josh Poimboeuf
2018-02-04 19:39 ` Dominik Brodowski
2018-02-05 14:18 ` David Woodhouse
2018-02-05 19:35 ` Tim Chen
2018-02-05 19:35 ` Tim Chen
-- strict thread matches above, loose matches on Subject: below --
2018-01-29 11:33 [PATCH] " David Woodhouse
2018-01-29 12:28 ` Dominik Brodowski
2018-01-29 12:44 ` David Woodhouse
2018-01-29 13:56 ` Dominik Brodowski
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=296de30b-515b-6eab-1b13-bb2f71451004@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linux-foundation.org \
--cc=karahmed@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 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.