public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lv Ying <lvying6@huawei.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <tony.luck@intel.com>, <linux-edac@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <mchehab+huawei@kernel.org>
Subject: Re: [RFC PATCH] x86/mce/inject: Fix printk deadlock causing mce_timed_out panic
Date: Tue, 11 May 2021 10:44:40 +0800	[thread overview]
Message-ID: <20210511024440.GA186630@localhost.localdomain> (raw)
In-Reply-To: <YJkAikroIpzN1Fl3@zn.tnic>

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

      reply	other threads:[~2021-05-10 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210509053229.GA2477949@localhost.localdomain>
     [not found] ` <YJahM9PaZ7Jefkbi@zn.tnic>
2021-05-11  1:33   ` [RFC PATCH] x86/mce/inject: Fix printk deadlock causing mce_timed_out panic Lv Ying
2021-05-10  9:36     ` Borislav Petkov
2021-05-10  9:44       ` Borislav Petkov
2021-05-11  2:44         ` Lv Ying [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210511024440.GA186630@localhost.localdomain \
    --to=lvying6@huawei.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox