linux-kernel - Re: [PATCH] KVM: arm64: vgic-debug: Don't put unmarked LPIs

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: <172408829923.848017.11368160825024844050.b4-ty@linux.dev>
Date: Mon, 19 Aug 2024 17:25:47 +0000
From: Oliver Upton <oliver.upton@...ux.dev>
To: linux-kernel@...r.kernel.org,
	kvmarm@...ts.linux.dev,
	linux-arm-kernel@...ts.infradead.org,
	Zenghui Yu <yuzenghui@...wei.com>
Cc: Oliver Upton <oliver.upton@...ux.dev>,
	james.morse@....com,
	suzuki.poulose@....com,
	wanghaibin.wang@...wei.com,
	maz@...nel.org
Subject: Re: [PATCH] KVM: arm64: vgic-debug: Don't put unmarked LPIs

On Sat, 17 Aug 2024 18:15:41 +0800, Zenghui Yu wrote:
> If there were LPIs being mapped behind our back (i.e., between .start() and
> .stop()), we would put them at iter_unmark_lpis() without checking if they
> were actually *marked*, which is obviously not good.
> 
> Switch to use the xa_for_each_marked() iterator to fix it.
> 
> 
> [...]

Applied to kvmarm/fixes, thanks!

[1/1] KVM: arm64: vgic-debug: Don't put unmarked LPIs
      https://git.kernel.org/kvmarm/kvmarm/c/2240a50e6294

--
Best,
Oliver