From: Tao Cui <cui.tao@linux.dev>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: cui.tao@linux.dev, maobibo@loongson.cn, gaosong@loongson.cn,
zhaotianrui@loongson.cn, loongarch@lists.linux.dev,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@xen0n.name, nagachaithanya9911@gmail.com,
Tao Cui <cuitao@kylinos.cn>
Subject: Re: [PATCH v2 4/4] LoongArch: KVM: Reject repeated PCH-PIC CTRL_INIT
Date: Wed, 30 Sep 2026 09:15:38 +0800 [thread overview]
Message-ID: <0c8125ab-9c66-42e2-87dc-208956bd4d9d@linux.dev> (raw)
In-Reply-To: <CAAhV-H5GNKZSjB_MN2Vi7uhbf1q9nqqvsfwqF+THpkwk3dEhGQ@mail.gmail.com>
Hi, Huacai.
在 2026/9/29 20:43, Huacai Chen 写道:
> Hi, Tao,
>
> On Tue, Sep 29, 2026 at 6:29 PM Tao Cui <cui.tao@linux.dev> wrote:
>>
>> From: Tao Cui <cuitao@kylinos.cn>
>>
>> KVM_DEV_LOONGARCH_PCH_PIC_CTRL_INIT has no guard against repeated
>> invocation: every call overwrites pch_pic_base and registers the same
>> kvm_io_device on the MMIO bus at the new address, while
>> kvm_pch_pic_destroy() unregisters only one bus range. After a repeated
>> init, MMIO to the stale ranges computes its register offset against the
>> new base and silently reads 0 / drops writes, and the leftover bus
>> entries persist until the VM is destroyed.
>>
>> Reject repeated initialization with -EEXIST, tracking the state with
>> a has_init flag so the check and the MMIO base update are atomic
>> under slots_lock. The base is only committed after a successful bus
>> registration, and the real registration error is propagated instead
>> of being replaced with -EFAULT.
>>
>> Fixes: d206d9514873 ("LoongArch: KVM: Add PCHPIC user mode read and write functions")
>> Signed-off-by: Tao Cui <cuitao@kylinos.cn>
>> ---
>> arch/loongarch/include/asm/kvm_pch_pic.h | 1 +
>> arch/loongarch/kvm/intc/pch_pic.c | 12 ++++++++++--
>> 2 files changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/loongarch/include/asm/kvm_pch_pic.h b/arch/loongarch/include/asm/kvm_pch_pic.h
>> index 887b0431fd20..679132d840e6 100644
>> --- a/arch/loongarch/include/asm/kvm_pch_pic.h
>> +++ b/arch/loongarch/include/asm/kvm_pch_pic.h
>> @@ -53,6 +53,7 @@ struct loongarch_pch_pic {
>> spinlock_t lock;
>> struct kvm *kvm;
>> struct kvm_io_device device;
>> + bool has_init;
>> union pch_pic_id id;
>> uint64_t mask; /* 1:disable irq, 0:enable irq */
>> uint64_t htmsi_en; /* 1:msi */
>> diff --git a/arch/loongarch/kvm/intc/pch_pic.c b/arch/loongarch/kvm/intc/pch_pic.c
>> index 7a704f18880d..a884a043feef 100644
>> --- a/arch/loongarch/kvm/intc/pch_pic.c
>> +++ b/arch/loongarch/kvm/intc/pch_pic.c
>> @@ -282,16 +282,24 @@ static int kvm_pch_pic_init(struct kvm_device *dev, u64 addr)
>> struct kvm_io_device *device;
>> struct loongarch_pch_pic *s = dev->kvm->arch.pch_pic;
> Why so complicated? The below is enough, no?
>
Thanks for the suggestion.
I agree that a separate has_init flag can be unnecessary here. v3 uses
s->device.ops to track whether the device has already been initialized.
The other changes are kept: pch_pic_base is updated only after
successful bus registration, and the original registration error is
returned instead of -EFAULT.
Thanks,
Tao
> diff --git a/arch/loongarch/kvm/intc/pch_pic.c
> b/arch/loongarch/kvm/intc/pch_pic.c
> index 2b63b0c2c7ce..7855d78304b7 100644
> --- a/arch/loongarch/kvm/intc/pch_pic.c
> +++ b/arch/loongarch/kvm/intc/pch_pic.c
> @@ -281,6 +281,9 @@ static int kvm_pch_pic_init(struct kvm_device
> *dev, u64 addr)
> struct kvm_io_device *device;
> struct loongarch_pch_pic *s = dev->kvm->arch.pch_pic;
>
> + if (s->device->ops)
> + return -EEXIST;
> +
> s->pch_pic_base = addr;
> device = &s->device;
> /* init device by pch pic writing and reading ops */
>
>>
>> - s->pch_pic_base = addr;
>> device = &s->device;
>> /* init device by pch pic writing and reading ops */
>> kvm_iodevice_init(device, &kvm_pch_pic_ops);
>> mutex_lock(&kvm->slots_lock);
>> + if (s->has_init) {
>> + ret = -EEXIST;
>> + goto out;
>> + }
>> /* register pch pic device */
>> ret = kvm_io_bus_register_dev(kvm, KVM_MMIO_BUS, addr, PCH_PIC_SIZE, device);
>> + if (!ret) {
>> + s->pch_pic_base = addr;
>> + s->has_init = true;
>> + }
>> +out:
>> mutex_unlock(&kvm->slots_lock);
>>
>> - return (ret < 0) ? -EFAULT : 0;
>> + return ret;
>> }
>>
>> /* used by user space to get or set pch pic registers */
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2026-09-30 1:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 10:28 [PATCH v2 0/4] LoongArch: KVM: irqchip fixes Tao Cui
2026-09-29 10:28 ` [PATCH v2 1/4] LoongArch: KVM: Clear device pointer in irqchip destroy callbacks Tao Cui
2026-09-29 10:42 ` sashiko-bot
2026-09-29 10:28 ` [PATCH v2 2/4] LoongArch: KVM: Load dmsintc pointer once in pch_msi_set_irq Tao Cui
2026-09-30 1:42 ` Bibo Mao
2026-09-30 2:08 ` Huacai Chen
2026-09-30 2:15 ` Bibo Mao
2026-09-29 10:28 ` [PATCH v2 3/4] LoongArch: KVM: Propagate real error code in kvm_pch_pic_create Tao Cui
2026-09-29 10:28 ` [PATCH v2 4/4] LoongArch: KVM: Reject repeated PCH-PIC CTRL_INIT Tao Cui
2026-09-29 12:43 ` Huacai Chen
2026-09-30 1:15 ` Tao Cui [this message]
2026-09-30 2:25 ` Huacai Chen
2026-09-30 1:54 ` Bibo Mao
2026-09-30 2:24 ` Huacai Chen
2026-09-30 2:34 ` Bibo Mao
2026-09-30 8:52 ` Huacai Chen
2026-09-30 9:05 ` Bibo Mao
2026-10-12 6:37 ` Huacai Chen
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=0c8125ab-9c66-42e2-87dc-208956bd4d9d@linux.dev \
--to=cui.tao@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=cuitao@kylinos.cn \
--cc=gaosong@loongson.cn \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=nagachaithanya9911@gmail.com \
--cc=zhaotianrui@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.