lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YJkAikroIpzN1Fl3@zn.tnic>
Date:   Mon, 10 May 2021 11:44:42 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Lv Ying <lvying6@...wei.com>
Cc:     linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
        tony.luck@...el.com, fanwentao@...wei.com, xujing99@...wei.com,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Subject: Re: [RFC PATCH] x86/mce/inject: Fix printk deadlock causing
 mce_timed_out panic

+ 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ