OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: devel@openvz.org, Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 v3 0/1] vfio: kvm reference leak on live update
Date: Thu, 05 Nov 2026 18:51:38 +0100	[thread overview]
Message-ID: <179390109818.2925323.7150229271114101935.b4-ty@b4> (raw)
In-Reply-To: <20261105141759.750676-1-andrey.drobyshev@virtuozzo.com>

On Thu, 05 Nov 2026 16:17:58 +0200, Andrey Drobyshev wrote:
> vfio: kvm reference leak on live update
> 
> A live update keeps the passthrough device open while the VM is
> re-created. The device holds a reference to the kvm it was opened
> with, so the first VM is never destroyed until the device closes. Take
> that reference only for the drivers that read device->kvm.
> 
> [...]

Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.19.vz10, thanks!

[1/1] vfio: take the kvm reference only for drivers that read device->kvm
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/d83d59385873

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team


_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-05 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 14:17 Andrey Drobyshev
2026-11-05 14:17 ` [Devel] [PATCH hci-8.1 v3 1/1] vfio: take the kvm reference only for drivers that read device->kvm Andrey Drobyshev
2026-11-05 14:22   ` no-reply
2026-11-05 17:51   ` Konstantin Khorenko
2026-11-05 17:51 ` [Devel] [PATCH hci-8.1 v3 0/1] vfio: kvm reference leak on live update Konstantin Khorenko
2026-11-05 17:51 ` Konstantin Khorenko [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=179390109818.2925323.7150229271114101935.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=andrey.drobyshev@virtuozzo.com \
    --cc=devel@openvz.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