From: Bibo Mao <maobibo@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>,
Xianglai Li <lixianglai@loongson.cn>
Cc: WANG Xuerui <kernel@xen0n.name>,
kvm@vger.kernel.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Move copy_from_user out of preempt disabled context
Date: Tue, 2 Sep 2025 17:49:41 +0800 [thread overview]
Message-ID: <20250902094945.2957566-1-maobibo@loongson.cn> (raw)
Function copy_from_user() and copy_to_user() may sleep because of page
fault, and they cannot be called with preempt disabled context, such as
spin_lock hold context.
Here this patch set move copy_from_user out of preempt disabled context,
local variable is added in spinlock context at first and then put to user
memory from local variable without spinlock.
Bibo Mao (4):
LoongArch: KVM: Avoid use copy_from_user with lock hold in
kvm_eiointc_regs_access
LoongArch: KVM: Avoid use copy_from_user with lock hold in
kvm_eiointc_sw_status_access
LoongArch: KVM: Avoid use copy_from_user with lock hold in
kvm_eiointc_ctrl_access
LoongArch: KVM: Avoid use copy_from_user with lock hold in
kvm_pch_pic_regs_access
arch/loongarch/kvm/intc/eiointc.c | 87 +++++++++++++++++++------------
arch/loongarch/kvm/intc/pch_pic.c | 22 +++++---
2 files changed, 68 insertions(+), 41 deletions(-)
base-commit: b320789d6883cc00ac78ce83bccbfe7ed58afcf0
--
2.39.3
next reply other threads:[~2025-09-02 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 9:49 Bibo Mao [this message]
2025-09-02 9:49 ` [PATCH 1/4] LoongArch: KVM: Avoid use copy_from_user with lock hold in kvm_eiointc_regs_access Bibo Mao
2025-09-02 11:58 ` Huacai Chen
2025-09-02 12:15 ` Bibo Mao
2025-09-03 8:34 ` Huacai Chen
2025-09-02 9:49 ` [PATCH 2/4] LoongArch: KVM: Avoid use copy_from_user with lock hold in kvm_eiointc_sw_status_access Bibo Mao
2025-09-02 9:49 ` [PATCH 3/4] LoongArch: KVM: Avoid use copy_from_user with lock hold in kvm_eiointc_ctrl_access Bibo Mao
2025-09-02 9:49 ` [PATCH 4/4] LoongArch: KVM: Avoid use copy_from_user with lock hold in kvm_pch_pic_regs_access Bibo Mao
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=20250902094945.2957566-1-maobibo@loongson.cn \
--to=maobibo@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixianglai@loongson.cn \
--cc=loongarch@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).