linux-kernel - Re: [PATCH] x86/PAT: Report PAT on CPUs that support PAT without MTRR

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: <09fee965-9cf2-110c-4484-d00bddb6b782@suse.com>
Date:   Wed, 13 Jul 2022 07:55:03 +0200
From:   Jan Beulich <jbeulich@...e.com>
To:     Chuck Zmudzinski <brchuckz@...scape.net>
Cc:     Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        Sean Christopherson <seanjc@...gle.com>,
        xen-devel@...ts.xenproject.org, Juergen Gross <jgross@...e.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/PAT: Report PAT on CPUs that support PAT without MTRR

On 12.07.2022 21:48, Chuck Zmudzinski wrote:
> I will also re-compile and test the new patch before sending
> v2 and unless Jan objects, I should acknowledge Jan as co-author
> of the patch since I will be using parts of his proposed patch
> to fix the "nopat" issue, so I also need to get his sign-off before
> sending v2. Jan, how should I obtain your sign-off?

If you really re-use any meaningful part, I think you could simply
propagate it from the patch I had sent. But I'd expect the pieces
to be too minor to actually warrant that.

Jan