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] [day] [month] [year] [list]
Message-ID: <20210305131804.GA2685@zn.tnic>
Date:   Fri, 5 Mar 2021 14:18:04 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Mike Travis <mike.travis@....com>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Steve Wahl <steve.wahl@....com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, Russ Anderson <rja@....com>,
        Dimitri Sivanich <dimitri.sivanich@....com>,
        Russ Anderson <russ.anderson@....com>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86/platform/uv: Add set of kernel block size for
 hubless arches

On Thu, Mar 04, 2021 at 04:39:55PM -0600, Mike Travis wrote:
> The commit below added a call to set the block size value that is needed
> to set the value used by the kernel.  This was done for UV Hubbed systems.
> This commit adds that same set call to hubless systems which supports the
> same NVRAMS and Intel BIOS thus the same problem occurs.
> 
> Fixes: bbbd2b51a2aa ...

The format is:

Fixes: bbbd2b51a2aa ("x86/platform/UV: Use new set memory block size function")

and you don't need to paste the commit text.

And if you add a Fixes tag, then this is supposed to fix something but
I'm unclear what exactly this fixes?

IOW, should this patch be backported to stable because UV hubless
systems would somehow fail without it?

Thx.

-- 
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