The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Zeng Chi <zeng_chi911@163.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,  zengchi@kylinos.cn,
	stable@vger.kernel.org
Subject: Re: [PATCH] KVM: Remove the kvm debugfs directory if kvm_init() fails
Date: Fri, 7 Aug 2026 07:11:38 -0700	[thread overview]
Message-ID: <anXnmvp2_Rj62huS@google.com> (raw)
In-Reply-To: <20260807071934.786879-1-zeng_chi911@163.com>

On Fri, Aug 07, 2026, Zeng Chi wrote:
> From: zengchi <zengchi@kylinos.cn>
> 
> kvm_init_debug() creates the "kvm" debugfs directory along with all of
> the VM/vCPU stat files, but none of kvm_init()'s error paths removes it.
> If kvm_vfio_ops_init(), kvm_gmem_init(), kvm_init_virtualization() or
> misc_register() fails, the directory is leaked, and none of kvm_init()'s
> callers invokes kvm_exit() on failure, i.e. nothing papers over the
> leak.
> 
> The stale /sys/kernel/debug/kvm directory isn't just cosmetic: a
> subsequent attempt to load KVM makes debugfs_create_dir() fail with
> -EEXIST, after which kvm_debugfs_dir holds an ERR_PTR and all stat
> files are silently never created again.  Worse, the leaked stat files
> reference file_operations and stat data that live in the KVM module; if
> the module is unloaded after the failed initialization, reading the
> stale files is a use-after-free.
> 
> Remove the debugfs directory in the error path, mirroring kvm_exit().
> 
> Fixes: 2b0128127373 ("KVM: Register /dev/kvm as the _very_ last thing during initialization")
> Cc: stable@vger.kernel.org
> Signed-off-by: zengchi <zengchi@kylinos.cn>
> ---
>  virt/kvm/kvm_main.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 45e784462ec6..8a503ac1adbd 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -6553,6 +6553,7 @@ int kvm_init(unsigned vcpu_size, unsigned vcpu_align, struct module *module)
>  err_gmem:
>  	kvm_vfio_ops_exit();
>  err_vfio:
> +	debugfs_remove_recursive(kvm_debugfs_dir);
>  	kvm_async_pf_deinit();
>  err_async_pf:
>  	kvm_irqfd_exit();
> -- 

Already posted (twice) and applied:

https://lore.kernel.org/all/20260706095910.39798-1-leixiang@kylinos.cn

  reply	other threads:[~2026-08-07 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  7:19 [PATCH] KVM: Remove the kvm debugfs directory if kvm_init() fails Zeng Chi
2026-08-07 14:11 ` Sean Christopherson [this message]
2026-08-07 22:46   ` Huang, Kai
2026-08-07 23:06     ` 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=anXnmvp2_Rj62huS@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=zeng_chi911@163.com \
    --cc=zengchi@kylinos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox