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: <20190107112430.GA28223@nazgul.tnic>
Date:   Mon, 7 Jan 2019 12:24:30 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     "S, Shirish" <Shirish.S@....com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H . Peter Anvin" <hpa@...or.com>,
        "maintainer : X86 ARCHITECTURE" <x86@...nel.org>,
        Tony Luck <tony.luck@...el.com>,
        Vishal Verma <vishal.l.verma@...el.com>,
        "open list : X86 ARCHITECTURE" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] x86/mce/amd: apply missing quirks for family 15
 models

On Mon, Jan 07, 2019 at 10:37:07AM +0000, S, Shirish wrote:
> This patch series applies to family 15 CPU's of AMD platforms,
> so as to address a consistent warning of
>  "[Firmware Bug]: cpu 0, invalid threshold interrupt offset"
> at every boot and upon completiong of successful S3 cycle,
> due to a missing quirk, which was not extended to newer models
> and also not applied in resume path.
> 
> Shirish S (2):
>   x86/mce/amd: Extend "Disable error thresholding bank 4" to more models
>   x86/mce/amd: Ensure quirks are applied in resume path as well
> 
>  arch/x86/kernel/cpu/mce/amd.c  | 34 ++++++++++++++++++++++++++++++++++
>  arch/x86/kernel/cpu/mce/core.c |  2 +-
>  2 files changed, 35 insertions(+), 1 deletion(-)
> 
> -- 

You sent those once three days ago. Why are you sending them again?
There's no changelog to explain what the difference is from the last
submission so what's up?

Also, I'd suggest you have more patience. And while you wait, you can
take a look at

https://www.kernel.org/doc/html/latest/process/submitting-patches.html

to read up on all the modalities when sending patches.

Thx.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ