From: Borislav Petkov <bp@alien8.de>
To: Lv Ying <lvying6@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
tony.luck@intel.com, fanwentao@huawei.com, xujing99@huawei.com
Subject: Re: [RFC PATCH] x86/mce/inject: Fix printk deadlock causing mce_timed_out panic
Date: Mon, 10 May 2021 11:36:04 +0200 [thread overview]
Message-ID: <YJj+hHBEi8sYMp79@zn.tnic> (raw)
In-Reply-To: <20210510200424.GA4056660@localhost.localdomain>
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
next prev parent reply other threads:[~2021-05-10 9:36 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 ` Lv Ying
2021-05-10 9:36 ` Borislav Petkov [this message]
2021-05-10 9:44 ` Borislav Petkov
2021-05-11 2:44 ` Lv Ying
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=YJj+hHBEi8sYMp79@zn.tnic \
--to=bp@alien8.de \
--cc=fanwentao@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvying6@huawei.com \
--cc=tony.luck@intel.com \
--cc=xujing99@huawei.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
all inboxes | Powered by JetHome®