From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x225urdllL0rVT79lF7XaMok/1kvFI+TuUBCfr7vvzevYkA+1obHzfEc97Rv5HCX/zRIjAfDE ARC-Seal: i=1; a=rsa-sha256; t=1517349456; cv=none; d=google.com; s=arc-20160816; b=YYUJAGLF/GmbJjZOScG+BeODikLfLwFIn6jXzCatjKkcHjv2NZTQ9D5P7rgW0xEkUt Yast02KJq1Abn7G8Qk9fVyDAM5KoyzDISJVZ33aHjvZbOaffzN7KEmrOLfjTslNeYpUb i7pc0tQdZYVKVyDphmX3EQfm/6oJpXBvd6gf8t5P7fOB+twYMRtU52/Uu+gT4e6ERNrc +d6cfGOU3cxLjOnVz2J5CdDCi60DHvGpDrhXTRvr7GRuP1vdsoj48dvD6ls0hDZ/L1qR FG/IbBQD0VBnix/T/VSzVZpeHAqv6zFabKK6EIOC+Q9iRTO9hQoY4ag9Sk63NfAPhd8X e/Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:arc-authentication-results; bh=1BImLqRFORVdsb5IqdYUWgmuR7KogvRwSDYXYrzN7kM=; b=y8jflbwyLpSGVY0cF7cXTrKANDEl19ykNSAvEuArKiJoIB6mhGmn7Jj2NpMwPyieH1 LKi9eNLQ7cH5+VIZ6FWxnyUda1qAL84UGLlVsdtVADTS37HHWClDNDMvAxfSiiT7Nmvc /bnI6ml8KR0vOvK64c5gaVUo+PgVgqexO2ilVxY9jBkC6PuIa6idjDywimoET7fk9fNj XrNq1Q+xVkiqD4Jo4PkLHTb3TizXVUAp9zmjAiE6yuGaElmZ+bfQb8VOZrZJiz0zAJ5c m9Uq0syC5u1/+MN/P6HLdSHbU6zXPD01b6CG1GnvmwQ5LUVgVDh0Coj5DGjKdWRqq7Hf /+2w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of bp@alien8.de designates 2a01:4f8:190:11c2::b:1457 as permitted sender) smtp.mailfrom=bp@alien8.de Authentication-Results: mx.google.com; spf=pass (google.com: domain of bp@alien8.de designates 2a01:4f8:190:11c2::b:1457 as permitted sender) smtp.mailfrom=bp@alien8.de Date: Tue, 30 Jan 2018 22:57:31 +0100 From: Borislav Petkov To: Tim Chen Cc: David Woodhouse , 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 Message-ID: <20180130215731.pszc5u4gcc32ds4v@pd.tnic> References: <1517263487-3708-1-git-send-email-dwmw@amazon.co.uk> <20180130203836.bsgme6kf6hstgbrx@pd.tnic> <024dd53b-1912-34fa-deb8-550c111df521@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <024dd53b-1912-34fa-deb8-550c111df521@linux.intel.com> User-Agent: NeoMutt/20170609 (1.8.3) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1590966106432961445?= X-GMAIL-MSGID: =?utf-8?q?1591056223970158916?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: 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. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.