From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] KVM: Do not leak memory for duplicate debugfs directories
Date: Thu, 5 Aug 2021 15:49:05 +1000 [thread overview]
Message-ID: <b2d4af96-ea66-982f-54c0-919546d39aa3@ozlabs.ru> (raw)
In-Reply-To: <20210804093737.2536206-1-pbonzini@redhat.com>
On 8/4/21 19:37, Paolo Bonzini wrote:
> KVM creates a debugfs directory for each VM in order to store statistics
> about the virtual machine. The directory name is built from the process
> pid and a VM fd. While generally unique, it is possible to keep a
> file descriptor alive in a way that causes duplicate directories, which
> manifests as these messages:
>
> [ 471.846235] debugfs: Directory '20245-4' with parent 'kvm' already present!
>
> Even though this should not happen in practice, it is more or less
> expected in the case of KVM for testcases that call KVM_CREATE_VM and
> close the resulting file descriptor repeatedly and in parallel.
>
> When this happens, debugfs_create_dir() returns an error but
> kvm_create_vm_debugfs() goes on to allocate stat data structs which are
> later leaked. The slow memory leak was spotted by syzkaller, where it
> caused OOM reports.
>
> Since the issue only affects debugfs, do a lookup before calling
> debugfs_create_dir, so that the message is downgraded and rate-limited.
> While at it, ensure kvm->debugfs_dentry is NULL rather than an error
> if it is not created. This fixes kvm_destroy_vm_debugfs, which was not
> checking IS_ERR_OR_NULL correctly.
>
> Cc: stable@vger.kernel.org
> Fixes: 536a6f88c49d ("KVM: Create debugfs dir and stat files for each VM")
> Reported-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
after another try, works brilliant.
Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Tested-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Thanks,
> ---
> virt/kvm/kvm_main.c | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index d20fba0fc290..b50dbe269f4b 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -892,6 +892,8 @@ static void kvm_destroy_vm_debugfs(struct kvm *kvm)
>
> static int kvm_create_vm_debugfs(struct kvm *kvm, int fd)
> {
> + static DEFINE_MUTEX(kvm_debugfs_lock);
> + struct dentry *dent;
> char dir_name[ITOA_MAX_LEN * 2];
> struct kvm_stat_data *stat_data;
> const struct _kvm_stats_desc *pdesc;
> @@ -903,8 +905,20 @@ static int kvm_create_vm_debugfs(struct kvm *kvm, int fd)
> return 0;
>
> snprintf(dir_name, sizeof(dir_name), "%d-%d", task_pid_nr(current), fd);
> - kvm->debugfs_dentry = debugfs_create_dir(dir_name, kvm_debugfs_dir);
> + mutex_lock(&kvm_debugfs_lock);
> + dent = debugfs_lookup(dir_name, kvm_debugfs_dir);
> + if (dent) {
> + pr_warn_ratelimited("KVM: debugfs: duplicate directory %s\n", dir_name);
> + dput(dent);
> + mutex_unlock(&kvm_debugfs_lock);
> + return 0;
> + }
> + dent = debugfs_create_dir(dir_name, kvm_debugfs_dir);
> + mutex_unlock(&kvm_debugfs_lock);
> + if (IS_ERR(dent))
> + return 0;
>
> + kvm->debugfs_dentry = dent;
> kvm->debugfs_stat_data = kcalloc(kvm_debugfs_num_entries,
> sizeof(*kvm->debugfs_stat_data),
> GFP_KERNEL_ACCOUNT);
> @@ -5201,7 +5215,7 @@ static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm)
> }
> add_uevent_var(env, "PID=%d", kvm->userspace_pid);
>
> - if (!IS_ERR_OR_NULL(kvm->debugfs_dentry)) {
> + if (kvm->debugfs_dentry) {
> char *tmp, *p = kmalloc(PATH_MAX, GFP_KERNEL_ACCOUNT);
>
> if (p) {
>
--
Alexey
prev parent reply other threads:[~2021-08-05 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 9:37 Paolo Bonzini
2021-08-04 9:56 ` Greg Kroah-Hartman
2021-08-04 23:32 ` Alexey Kardashevskiy
2021-08-04 23:53 ` Alexey Kardashevskiy
2021-08-05 5:49 ` Alexey Kardashevskiy [this message]
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=b2d4af96-ea66-982f-54c0-919546d39aa3@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.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®