linux-kernel - Re: [PATCH v2] x86: lib: Separate instruction decoder MMIO type from MMIO trace

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: <Y7L4n0imic1ncHhe@zn.tnic>
Date:   Mon, 2 Jan 2023 16:30:39 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
Cc:     tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
        x86@...nel.org, hpa@...or.com,
        Ricardo Neri <ricardo.neri-calderon@...ux.intel.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] x86: lib: Separate instruction decoder MMIO type from
 MMIO trace

On Mon, Jan 02, 2023 at 03:49:23PM +0100, Jason A. Donenfeld wrote:
> Do you think you could queue up this patch for 6.2 as a fix? It has
> basically no chance of breakage and does fix a real symbol clash.
> 
> https://lore.kernel.org/lkml/20221214203454.337299-1-Jason@zx2c4.com/
>
> This doesn't fix any existing compile error that I'm aware of, but if
> this makes it into 6.2, it would avoid me having to carry it in a series
> I'm working on,...

Our general rule for urgent fixes going through tip is that they should qualify
to be CC:stable fixes. And this one isn't so I think you should hold on to it
and submit it along with the whole series as it is usually done.

Thx.

-- 
Regards/Gruss,
    Boris.

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