linux-kernel - Re: [tip: x86/entry] x86/entry: Avoid redundant CR3 write on paranoid returns

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: <20240219144210.GDZdNowiz8Tr9j8acY@fat_crate.local>
Date: Mon, 19 Feb 2024 15:42:10 +0100
From: Borislav Petkov <bp@...en8.de>
To: Brendan Jackman <jackmanb@...gle.com>
Cc: linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
	Lai Jiangshan <laijs@...ux.alibaba.com>,
	Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
	Kevin Cheng <chengkev@...gle.com>,
	Yosry Ahmed <yosryahmed@...gle.com>
Subject: Re: [tip: x86/entry] x86/entry: Avoid redundant CR3 write on
 paranoid returns

On Mon, Feb 19, 2024 at 11:49:46AM +0100, Brendan Jackman wrote:
> [Apologies if you see this as a duplicate, accidentally sent the
> original in HTML, please disregard the other one]
> 
> Hi Thomas,
> 
> I have just noticed that the commit has disappeared from
> tip/x86/entry. Is that deliberate?

$ git fetch tip
$ git log -1 --oneline tip/x86/entry
bb998361999e (refs/remotes/tip/x86/entry) x86/entry: Avoid redundant CR3 write on paranoid returns

Looks there to me. :)

-- 
Regards/Gruss,
    Boris.

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