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.1 required=3.0 tests=BAYES_00,DATE_IN_FUTURE_12_24, 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 461A6C433ED for ; Mon, 10 May 2021 10:37:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0B5A9619C6 for ; Mon, 10 May 2021 10:37:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231757AbhEJKi6 (ORCPT ); Mon, 10 May 2021 06:38:58 -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