Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2462498pxj; Mon, 10 May 2021 03:40:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyT0+XXJ2bnVgGGPa3/QotkofEueEy3X/Kk0fNVy4NnqJYonjrAqjloK5dmcSo9qy4in2a6 X-Received: by 2002:a17:906:14c1:: with SMTP id y1mr25716635ejc.481.1620643225818; Mon, 10 May 2021 03:40:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620643225; cv=none; d=google.com; s=arc-20160816; b=csLKokWqbgu8RSqM5lE/eX2CmKaqsvAuCf+pRcJOqs1PHvHDEFZ14JCsdAn7P/ssTT MDQSa1un3Et4KIHdWozjSqCWmPJ76vmmvUrCot5AOmidZIXKR4UKqiPuYTClVyTtTK7S h2wRzopjXcCCO5U8S+UvLHC5YHKWLJqQbm8/8cwpmUDkDEk3lhkdLf2gzObBQZFbyiHF 2AFX/VK0SzD4R+CMghnaCooLAhkvz6cqaBChb2AKvfVIol2552zToBmjjovwRFyRM05Z 9R1tiZqCSbDRtdu5lCRz9I6TKbL8YUbGjnctM/RDyXMCViCgPnBVZpZfAPCL/dKJPFsL +RkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=7txrwNScE3o3olIXII4TPv37ffkRAfa00vrkZsBR9og=; b=KXMU/Oe3kUBTPDOlK5wWpt3Z9ff0u8HK4gimsLAHWLeCQVytOD4DI49toRxg9X4aG1 eIjAyd5hUlbY+gC5qGCwSmH+/wa9MOJRsydNa7q6K7ARJx/ZAYO9fF40dh7qKmi83lIu yfEpecMkQlk4HepACdVQXrir71T2S0wFbZTeUm7vDAQQwvEGA9W4KdTEJ4m6ipB19vi3 GGfXqqxDmOkAmdJLL3VDsxXrASq2UV+gCoffOPVsJ3s+IegBcRu1XLGc6GWWsXfhI53i B1DOMqZmLvyc1Uq3M92d0bbC7Ro+eBQd6dDkcHyPa9f8379Jo2CKTlafZBrFSluAf8bS VvtQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id zb13si328163ejb.487.2021.05.10.03.39.59; Mon, 10 May 2021 03:40:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230285AbhEJKiv (ORCPT + 99 others); Mon, 10 May 2021 06:38:51 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:2549 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232304AbhEJKeU (ORCPT ); Mon, 10 May 2021 06:34:20 -0400 Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4Fdy4W51KszkY1f; Mon, 10 May 2021 18:30:35 +0800 (CST) Received: from localhost.localdomain (10.175.101.6) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server (TLS) id 14.3.498.0; Mon, 10 May 2021 18:33:09 +0800 Date: Tue, 11 May 2021 10:44:40 +0800 From: Lv Ying To: Borislav Petkov CC: , , , Subject: Re: [RFC PATCH] x86/mce/inject: Fix printk deadlock causing mce_timed_out panic Message-ID: <20210511024440.GA186630@localhost.localdomain> References: <20210509053229.GA2477949@localhost.localdomain> <20210510200424.GA4056660@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Originating-IP: [10.175.101.6] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 10, 2021 at 11:44:42AM +0200, Borislav Petkov wrote: > + Mauro. > > On Mon, May 10, 2021 at 11:36:04AM +0200, Borislav Petkov wrote: > > On Tue, May 11, 2021 at 09:33:10AM +0800, Lv Ying wrote: > > > This panic happend on 4.18 kernel > > > > When you report bugs and send patches to lkml and maintainers, *always* > > do that against the latest upstream version. > > > > This is not the first time people from Huawei send bug reports and > > "fixes" for old kernels. > > > > Please let your colleagues and whoever else at Huawei is sending patches > > and reporting bugs - *always* test and report bugs against the latest > > upstream kernel - not some old version! > > > > If you want bugs against > > > > 4.18.0-147.5.1.6.h429.eulerosv2r10.x86_64 > > > > fixed, go report that to whoever has made that kernel - not upstream. > > > > Now, if you want to improve the upstream kernel and can trigger the same > > thing with the upstream kernel, pls give the *exact* full information I > > asked you before so that I am able to reproduce that here independently > > and then we can take it from there. > > > > HTH. > Boris, thanks again for your time to explain the detailed and standard upstream bug report process. Next, I will test on the latest upstream kernel(indpendent to any distro). If I can reproduce this problem, I will send detailed test script. Thanks Lv Ying