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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 5DFEEC433B4 for ; Mon, 10 May 2021 09:44:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 314B361468 for ; Mon, 10 May 2021 09:44:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230423AbhEJJpt (ORCPT ); Mon, 10 May 2021 05:45:49 -0400 Received: from mail.skyhub.de ([5.9.137.197]:36410 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229566AbhEJJpq (ORCPT ); Mon, 10 May 2021 05:45:46 -0400 Received: from zn.tnic (p200300ec2f066d00c3c3b9d774715f25.dip0.t-ipconnect.de [IPv6:2003:ec:2f06:6d00:c3c3:b9d7:7471:5f25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 956E71EC023E; Mon, 10 May 2021 11:44:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1620639880; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=h4xnkqlVtSYi7fjTjCl9phrCrkvVI4cLvRNnj6rGP5s=; b=WoqkZFrMmAakABSs+r7oW/XGS99uz74IQsJS8M6Ft6Ve8HBCkZ7UCCenI9Dj3jpZC+9iVS +QrqPOqKIcuUzUTJlyN16bS4NEzj0e5X6I+8GhLPtBXYtHdxPvLazikGuNueO9mCQJ6Aj0 ilM8eOjPf4hdHFxciwXlmrECkGzr0lY= Date: Mon, 10 May 2021 11:44:42 +0200 From: Borislav Petkov To: Lv Ying Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org, tony.luck@intel.com, fanwentao@huawei.com, xujing99@huawei.com, Mauro Carvalho Chehab Subject: Re: [RFC PATCH] x86/mce/inject: Fix printk deadlock causing mce_timed_out panic Message-ID: References: <20210509053229.GA2477949@localhost.localdomain> <20210510200424.GA4056660@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org + 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. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette