mirror of
git://git.proxmox.com/git/pve-storage.git
synced 2024-12-22 13:34:16 +03:00
don't bail on whitespaces in backing devices
This prevents importing from vmdks with whitespaces in file names. Further, some operations that include file sizes (like listing disks) would potentially fail entirely if a custom disk with a badly name backing device exists in a VM images directory since they don't expect this. Specifically, since we don't necessarily know the actual naming scheme of the current storage in the plain Plugin.pm version, we don't check the full name anyway, so why bother with whitespaces... See-also: https://forum.proxmox.com/threads/new-import-wizard-available-for-migrating-vmware-esxi-based-virtual-machines.144023/page-16#post-658697 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
This commit is contained in:
parent
bb72798064
commit
22cb4b0b78
@ -982,7 +982,7 @@ sub file_size_info {
|
||||
$used = int($used);
|
||||
($format) = ($format =~ /^(\S+)$/) or die "format '$format' includes whitespace\n"; # untaint
|
||||
if (defined($parent)) {
|
||||
($parent) = ($parent =~ /^(\S+)$/) or die "parent '$parent' includes whitespace\n"; # untaint
|
||||
($parent) = ($parent =~ /^(\S+)$/); # untaint
|
||||
}
|
||||
return wantarray ? ($size, $format, $used, $parent, $st->ctime) : $size;
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user