Proxmox/pve-common
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-common.git synced 2025-01-25 18:03:33 +03:00
Code Releases Activity

INotify.pm: use Clone::clone instead of Storable::dclone

Browse Source 
I run into seroius troubles with dclone, which seem to be
buggy with tainted flag ...

Also, documentation states Clone::clone is much faster.
This commit is contained in:
Dietmar Maurer 2017-03-21 11:56:49 +01:00
parent e04b9f4c43
commit 32ef45aee2
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/PVE/INotify.pm
View File

@ -15,7 +15,7 @@ use PVE::SafeSyslog;
use PVE::Exception qw(raise_param_exc);
use PVE::Tools;
use PVE::ProcFSTools;
use Storable qw(dclone);
use Clone qw(clone);
use Linux::Inotify2;
use base 'Exporter';
use JSON;
@ -247,7 +247,7 @@ sub read_file {
my $ret;
if (!$noclone && ref ($ccinfo->{data})) {
$ret->{data} = dclone ($ccinfo->{data});
$ret->{data} = clone ($ccinfo->{data});
} else {
$ret->{data} = $ccinfo->{data};
}
@ -269,7 +269,7 @@ sub read_file {
}
# we cache data with references, so we always need to
# dclone this data. Else the original data may get
# clone this data. Else the original data may get
# modified.
$ccinfo->{data} = $res;
@ -278,7 +278,7 @@ sub read_file {
my $ret;
if (!$noclone && ref ($ccinfo->{data})) {
$ret->{data} = dclone ($ccinfo->{data});
$ret->{data} = clone ($ccinfo->{data});
} else {
$ret->{data} = $ccinfo->{data};
}