From: "Jakob Klocker" <j.klocker@proxmox.com>
To: "Fiona Ebner" <f.ebner@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH pve-storage v2 1/2] qemu-img: drop unused image resize timeout parameter
Date: Tue, 11 Aug 2026 08:23:59 +0200 [thread overview]
Message-ID: <DKLWDV485B69.41Q60R3S2QVB@proxmox.com> (raw)
In-Reply-To: <0b7288d3-15d7-4024-86e9-0620671f21f5@proxmox.com>
On Thu Aug 6, 2026 at 3:04 PM CEST, Fiona Ebner wrote:
> Am 04.08.26 um 11:04 AM schrieb Jakob Klocker:
>> qemu_img_resize is only ever called with a hardcoded 10 second timeout,
>> so exposing it as a parameter serves no purpose.
>
> The Storage::Common module is a bit special, because we want to allow
> third-party plugins to re-use these methods too. There might already be
> a caller from outside our code-base which does use the parameter, so I'd
> rather keep it. The default value should still be adapted to fix the bug
> of course and our callers can rely on that.
>
> Of course, changing the default would also be an interface change, but I
> would consider it okay. Dropping the parameter is also a bit of a
> timebomb, becuase the next time we add a parameter, an existing caller
> currently passing a value for timeout would suddenly pass a value for
> the newly added parameter.
>
I didn't know about third-party plugins reusing Storage::Common - thanks
for pointing that out.
Since I couldn't find this documented anywhere, would it be worth noting
on the storage plugin development wiki page [0] that these helpers may
be reused?
[0] https://pve.proxmox.com/wiki/Storage_Plugin_Development
>>
>> Signed-off-by: Jakob Klocker <j.klocker@proxmox.com>
>> ---
>> src/PVE/Storage/Common.pm | 8 ++++----
>> src/PVE/Storage/LVMPlugin.pm | 2 +-
>> src/PVE/Storage/Plugin.pm | 2 +-
>> 3 files changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/src/PVE/Storage/Common.pm b/src/PVE/Storage/Common.pm
>> index 3932aee..725f623 100644
>> --- a/src/PVE/Storage/Common.pm
>> +++ b/src/PVE/Storage/Common.pm
>> @@ -259,16 +259,16 @@ sub qemu_img_measure {
>>
>> =head3 qemu_img_resize
>>
>> - qemu_img_resize($path, $format, $size, $preallocation, $timeout)
>> + qemu_img_resize($path, $format, $size, $preallocation)
next prev parent reply other threads:[~2026-08-11 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 9:04 [PATCH storage v2 0/2] fix #7598: qemu-img: increase timeout for image resize Jakob Klocker
2026-08-04 9:04 ` [PATCH pve-storage v2 1/2] qemu-img: drop unused image resize timeout parameter Jakob Klocker
2026-08-05 15:20 ` Elias Huhsovitz
2026-08-06 13:04 ` Fiona Ebner
2026-08-11 6:23 ` Jakob Klocker [this message]
2026-08-11 8:05 ` Fiona Ebner
2026-08-04 9:04 ` [PATCH pve-storage v2 2/2] fix #7598: qemu-img: increase timeout for image resizing in worker context Jakob Klocker
2026-08-05 15:30 ` Elias Huhsovitz
2026-08-11 7:40 ` superseded: [PATCH storage v2 0/2] fix #7598: qemu-img: increase timeout for image resize Jakob Klocker
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=DKLWDV485B69.41Q60R3S2QVB@proxmox.com \
--to=j.klocker@proxmox.com \
--cc=f.ebner@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