public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server 3/3] api: update vm: fork before locking
Date: Fri, 3 Jul 2026 13:44:45 +0200	[thread overview]
Message-ID: <1536da22-7e3b-41b9-b7f4-b9c7acfa80cf@proxmox.com> (raw)
In-Reply-To: <4d763f1f-59e0-4ad5-b7c1-72b4e5b65dd1@proxmox.com>

Am 03.07.26 um 11:41 AM schrieb Dominik Csapak:
> one remark/question:
> 
> would it make for a nicer interface for the load_and_check_config
> if we'd pass the delete list into it instead of using
> catching the outer closure variable?
> 
> that way we wouldn't have to guard the 'push @delete' statements
> and could simply pass an empty list into it when we don't want
> to add them.
> 
> the only difference it would make is that inside, we wouldn't
> delete the $conf->{lock} there but since we discard that
> before using it when we don't want to update delete this
> should be fine?

As discussed during lunch too, in case the vmstate is being deleted,
it's important that the load_and_check_config() gets the actual $delete
list. Because if we pass an empty list, then we don't delete the
suspended lock, and then the check_lock() right below would fail.

Of course, this could be handled by adapting the function with
additional arguments, but the guard seems rather straightforward to me,
so I would be inclined to just keep it like that.




  reply	other threads:[~2026-07-03 11:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 12:45 [PATCH-SERIES qemu-server 0/3] fix #7743: api: disk import: avoid locking twice when importing from OVA or same VM Fiona Ebner
2026-06-29 12:45 ` [PATCH qemu-server 1/3] api: disk import: remove unused wrongly named variable Fiona Ebner
2026-07-03  9:32   ` Dominik Csapak
2026-06-29 12:45 ` [PATCH qemu-server 2/3] fix #7743: api: disk import: avoid locking twice when importing from OVA or same VM Fiona Ebner
2026-07-03  9:31   ` Dominik Csapak
2026-06-29 12:45 ` [PATCH qemu-server 3/3] api: update vm: fork before locking Fiona Ebner
2026-07-03  9:41   ` Dominik Csapak
2026-07-03 11:44     ` Fiona Ebner [this message]
2026-07-03 12:00       ` Dominik Csapak
2026-06-30  9:49 ` [PATCH-SERIES qemu-server 0/3] fix #7743: api: disk import: avoid locking twice when importing from OVA or same VM Manuel Federanko
2026-07-03 11:59 ` superseded: " Fiona Ebner

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=1536da22-7e3b-41b9-b7f4-b9c7acfa80cf@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal