public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Jing Luo via pve-devel <pve-devel@lists.proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Jing Luo <jing@jing.rocks>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-manager 2/2] move /run/vzdump.lock to /run/lock/vzdump.lock
Date: Mon, 24 Mar 2025 20:41:17 +0900	[thread overview]
Message-ID: <mailman.130.1742816524.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <e4cca824-31d7-40e9-b6de-31cbb711b604@proxmox.com>

[-- Attachment #1: Type: message/rfc822, Size: 7475 bytes --]

[-- Attachment #1.1.1: Type: text/plain, Size: 1624 bytes --]

On 2025-03-24 17:02, Thomas Lamprecht wrote:
> Am 22.03.25 um 16:17 schrieb Jing Luo:
>> It's more appropriate under Debian, and vzdump.lock doesn't seem to
>> be used by any other package.
> 
> This is very dangerous and needs a ton of work to be done right.
> 
> As any vzdump job that started before a package update got installed 
> that
> includes this (and the others) patches and any job started afterwards 
> will
> not be protected at all.

My bad, for this patch I didn't think it through what the result could 
be. For
now let's drop this patch.

> Same for all other patches and the respective things they use the lock
> to protect against mutual access.
> 
> If this was done we would need to:
> - keep the old lock path for one major release around and always 
> acquire
>   the lock over the old path first for as long as we can safely say 
> that
>   no old job is running. For a lot of things this means until the next
>   reboot, as /run is tmpfs backed and thus will be cleared then anyway.
> 
> - need some actual good reason instead of "it's more appropriate" which
>   can be a fine argument for adding new lock paths but definitively not
>   enough to justify moving existing ones.
> 
> The same holds for all patches of this series.

What's wrong with other patches in the series? No lock file path is 
moved, b/c
/var/run is a symlink to /run and /var/lock is a symlink to /run/lock, 
unless
we have to account for non-Debian systems where /var/run and /var/lock 
are not
symlinks?

-- 
Jing Luo
About me: https://jing.rocks/about/
GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC

[-- Attachment #1.1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-03-24 11:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250322152004.1646886-1-jing@jing.rocks>
2025-03-22 15:17 ` Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH] rust-proxmox-network-api: change /var/lock to /run/lock Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pmg-api] tree-wide: change /var/run to /run and " Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH] rust-proxmox-backup: change " Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pve-cluster] tree-wide: change /var/run to /run and " Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pve-common] " Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pve-container] tree-wide: change /var/run to /run Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pve-firewall] tree-wide: change /var/run to /run and /var/lock to /run/lock Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pve-guest-common] tree-wide: change " Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH pve-storage] " Jing Luo via pve-devel
2025-03-22 15:17 ` [pve-devel] [PATCH qemu-server] tree-wide: change /var/run to /run and " Jing Luo via pve-devel
     [not found] ` <20250322152004.1646886-2-jing@jing.rocks>
2025-03-24  8:02   ` [pve-devel] [PATCH pve-manager 2/2] move /run/vzdump.lock to /run/lock/vzdump.lock Thomas Lamprecht
2025-03-24 11:41     ` Jing Luo via pve-devel [this message]
     [not found]     ` <d8306d3000f15b2dc4dad5f0be32db4f@jing.rocks>
2025-03-24 11:56       ` Thomas Lamprecht
2025-03-24 13:04         ` Jing Luo via pve-devel
     [not found]         ` <39e9a7cd767a4de295ab573fa71c7722@jing.rocks>
2025-03-24 13:11           ` Thomas Lamprecht

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=mailman.130.1742816524.359.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=jing@jing.rocks \
    --cc=t.lamprecht@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