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: <20250113201905.GHZ4V1OQkgA44sty2k@fat_crate.local>
Date: Mon, 13 Jan 2025 21:19:05 +0100
From: Borislav Petkov <bp@...en8.de>
To: Marek Marczykowski-Górecki <marmarek@...isiblethingslab.com>
Cc: Mike Rapoport <rppt@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
	Juergen Gross <jgross@...e.com>, linux-kernel@...r.kernel.org,
	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>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86/execmem: fix ROX cache usage in Xen PV guests

On Mon, Jan 13, 2025 at 09:10:03PM +0100, Marek Marczykowski-Górecki wrote:
> I was running some tests today with the above patch on top of -rc7
> (and without Jürgen's one). Some tests are still running, and there are
> still some crashes I need to take a look at (could be completely
> unrelated), but generally it looks _much_ better, especially I don't see
> the wall of crashes in HVM domU that I've seen before
> (https://lore.kernel.org/xen-devel/Z3cyhdKu6M1vdBe_@mail-itl/).
> The latter could be an effect of the above fix, or could be some other
> fix that happened between -rc5 and -rc7. If that would be interesting,
> I can also re-test with -rc5 + the above patch, or something else. Let
> me know.

Yeah, we disabled that EXECMEM_ROX thing for now on x86, that close to the
merge window to avoid the fiasco:

https://git.kernel.org/tip/a9bbe341333109465605e8733bab0b573cddcc8c

and so this should fix all issues for you, I presume.

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