From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 01F45C3A5A1 for ; Sun, 25 Aug 2019 17:30:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D176A206BA for ; Sun, 25 Aug 2019 17:30:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728714AbfHYRaG (ORCPT ); Sun, 25 Aug 2019 13:30:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:58260 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728612AbfHYRaG (ORCPT ); Sun, 25 Aug 2019 13:30:06 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5A7E9B11B; Sun, 25 Aug 2019 17:30:05 +0000 (UTC) Date: Sun, 25 Aug 2019 19:30:00 +0200 From: Borislav Petkov To: Linus Torvalds Cc: Thomas Gleixner , Tom Lendacky , Linux List Kernel Mailing , the arch/x86 maintainers Subject: Re: [GIT pull] x86/urgent for 5.3-rc5 Message-ID: <20190825173000.GB20639@zn.tnic> References: <156672618029.19810.8479315461492191933.tglx@nanos.tec.linutronix.de> <156672618029.19810.9732807383797358917.tglx@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 25, 2019 at 10:18:02AM -0700, Linus Torvalds wrote: > Not doing the Zen 2 boot-time case? Everybody assumes that all > firmware has been fixed? My info is that all Zen has been taken care of with fw fixes. > That one should be easy to verify since it happens at boot: just do > "rdrand" twice, and if it returns all-ones both times, it's broken. Should we do that somewhere in the early boot code by adding a WARN_ON() or so and see who screams? -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 247165, AG München