mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "zoudongjie (A)" <zoudongjie@huawei.com>
To: "seanjc@google.com" <seanjc@google.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Chenzhendong (alex)" <alex.chen@huawei.com>,
	luolongmin <luolongmin@huawei.com>,
	"Mujinsheng (DxJanesir)" <mujinsheng@huawei.com>,
	"chenjianfei (D)" <chenjianfei3@huawei.com>,
	"Fangyi (Eric)" <eric.fangyi@huawei.com>,
	"lishan (E)" <lishan24@huawei.com>,
	Renxuming <renxuming@huawei.com>,
	suxiaodong <suxiaodong1@huawei.com>,
	"caijunjie (A)" <caijunjie15@h-partners.com>,
	"zoudongjie (A)" <zoudongjie@huawei.com>
Subject: [Question Consultation] KVM: x86: No lock protection was applied in handle_ept_misconfig of kernel 5.10?
Date: Wed, 9 Jul 2025 06:32:10 +0000	[thread overview]
Message-ID: <fb4c14aa629a4dddb44d0fa9c4f7b498@huawei.com> (raw)

Hi all,

I noticed that in handle_ept_misconfig(), kvm_io_bus_write() is called. And within kvm_io_bus_write(), BUS is obtained
through srcu_dereference(). During this process, kvm->slots_lock is not acquired, nor is srcu_read_lock() called for 
protection. If another process is synchronizing BUS at the same time, synchronize_srcu_expedited() cannot safely reclaim
space(it cannot protect srcu_dereference() outside the critical section?), how can we ensure that BUS obtained by
kvm_io_bus_write() is the latest?

Thanks,
Junjie Cai

Reported by: Junjie Cai <caijunjie15@h-partners.com>

             reply	other threads:[~2025-07-09  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09  6:32 zoudongjie (A) [this message]
2025-07-09 12:42 ` Sean Christopherson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb4c14aa629a4dddb44d0fa9c4f7b498@huawei.com \
    --to=zoudongjie@huawei.com \
    --cc=alex.chen@huawei.com \
    --cc=bp@alien8.de \
    --cc=caijunjie15@h-partners.com \
    --cc=chenjianfei3@huawei.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=eric.fangyi@huawei.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lishan24@huawei.com \
    --cc=luolongmin@huawei.com \
    --cc=mingo@redhat.com \
    --cc=mujinsheng@huawei.com \
    --cc=pbonzini@redhat.com \
    --cc=renxuming@huawei.com \
    --cc=seanjc@google.com \
    --cc=suxiaodong1@huawei.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®