linux-kernel - Re: [PATCH -next] x86/apic: Force logial APIC ID in range from 0 to 8

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]

Date:   Mon, 26 Apr 2021 13:09:30 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     xuyihang <xuyihang@...wei.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        "mingo@...nel.org" <mingo@...nel.org>,
        "x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
        "dwmw@...zon.co.uk" <dwmw@...zon.co.uk>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] x86/apic: Force logial APIC ID in range from 0 to 8

On Mon, Apr 26, 2021 at 02:09:59AM +0000, xuyihang wrote:
> Hi, I realize this problem only occur on kernel 3.10, and not on 4.18. Which leads me to this patch
> (https://lore.kernel.org/patchwork/patch/855026/). flat_init_apic_ldr should not be called in this case.
> 

This is not the first time people from Huawei are sending patches for
some old kernel to the *upstream* kernel mailing list.

You do know that we take patches only for the *upstream* kernel old
kernels are someone else's problem, right?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette