From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D18283F626A; Sat, 28 Feb 2026 17:42:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772300560; cv=none; b=MphNMhh0WgfuoEoHZYZvdlaGrlcmqdtGndNhkm/GPPuBYynBZK9esiwxlkw5j63fudYkBnvWDuKp5awREKD1uH8YoYVeZUUhWdd6AEA+ib+ejb4wSfAfGM/WJtsgptlaLDRSulisXG2O7bgVvRaLOgw1C9xDmcTsrzacPfpU1kI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772300560; c=relaxed/simple; bh=jmP9nu0tcyCOQ6ZWqCiraqPMH4qvU3M7wXK/4ccptq8=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=KWc1Y+NaGJDSC/MM2Ey6ufnogASUkn//sZfiYwQtjB8xvMrRmVT+M4xtCvh+1XzBODJ6KRKsH/Fd4gAyq4srzrCiunAeSML2r++rg6qPVJrbleOYQT5eSLGPkf1AgHL+UNaNKjXDNUoLhIqAvx/NLggIh7HmzNA0kmMGJR82EDE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=RalvNmLb; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="RalvNmLb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 121C1C19423; Sat, 28 Feb 2026 17:42:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772300560; bh=jmP9nu0tcyCOQ6ZWqCiraqPMH4qvU3M7wXK/4ccptq8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=RalvNmLb8QIrFeCuw0XswIQXyITk2JEXuvgMy4qljGt8l8ZmeVBq7LckTJ8SCxYQL CD0NCuqdF0aKeK7BP5kk+Pk6e/yBYicMm1FzhaRFcq8qHUdXwps6PTcUOVsMbn4J83 +rETeZySwnakDKH5F8CWuHxBDOMB14LBlwl56BUZ2UJ/cA0cWH3dwo6rs7BoVErwQT FJ/wleRu3G6Z2WE+cvTEtHdUrAYcpvYbal7yIU5ogMxsAWpmNTlsGtgKk7W3FuLdzk DlWCM7qrTwFi9c/p5CNA/DqvqqyCL5P4XTAC7N7va3THCKVjPZd+FQdY6CX3+uriqc K6ZEiJ2Qa0k3A== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Sean Christopherson , Alessandro Ratti , syzbot+1522459a74d26b0ac33a@syzkaller.appspotmail.com, Sasha Levin Subject: [PATCH 6.19 600/844] KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() Date: Sat, 28 Feb 2026 12:28:33 -0500 Message-ID: <20260228173244.1509663-601-sashal@kernel.org> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260228173244.1509663-1-sashal@kernel.org> References: <20260228173244.1509663-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit From: Sean Christopherson [ Upstream commit ead63640d4e72e6f6d464f4e31f7fecb79af8869 ] Ignore -EBUSY when checking nested events after exiting a blocking state while L2 is active, as exiting to userspace will generate a spurious userspace exit, usually with KVM_EXIT_UNKNOWN, and likely lead to the VM's demise. Continuing with the wakeup isn't perfect either, as *something* has gone sideways if a vCPU is awakened in L2 with an injected event (or worse, a nested run pending), but continuing on gives the VM a decent chance of surviving without any major side effects. As explained in the Fixes commits, it _should_ be impossible for a vCPU to be put into a blocking state with an already-injected event (exception, IRQ, or NMI). Unfortunately, userspace can stuff MP_STATE and/or injected events, and thus put the vCPU into what should be an impossible state. Don't bother trying to preserve the WARN, e.g. with an anti-syzkaller Kconfig, as WARNs can (hopefully) be added in paths where _KVM_ would be violating x86 architecture, e.g. by WARNing if KVM attempts to inject an exception or interrupt while the vCPU isn't running. Cc: Alessandro Ratti Cc: stable@vger.kernel.org Fixes: 26844fee6ade ("KVM: x86: never write to memory from kvm_vcpu_check_block()") Fixes: 45405155d876 ("KVM: x86: WARN if a vCPU gets a valid wakeup that KVM can't yet inject") Link: https://syzkaller.appspot.com/text?tag=ReproC&x=10d4261a580000 Reported-by: syzbot+1522459a74d26b0ac33a@syzkaller.appspotmail.com Closes: https://lore.kernel.org/all/671bc7a7.050a0220.455e8.022a.GAE@google.com Link: https://patch.msgid.link/20260109030657.994759-1-seanjc@google.com Signed-off-by: Sean Christopherson Signed-off-by: Sasha Levin --- arch/x86/kvm/x86.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 042ebda1a6576..d65ebaed18986 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -11609,8 +11609,7 @@ static inline int vcpu_block(struct kvm_vcpu *vcpu) if (is_guest_mode(vcpu)) { int r = kvm_check_nested_events(vcpu); - WARN_ON_ONCE(r == -EBUSY); - if (r < 0) + if (r < 0 && r != -EBUSY) return 0; } -- 2.51.0