On 4/1/20 12:20 PM, w.bumil...@proxmox.com wrote:
> From: Wolfgang Bumiller <w.bumil...@proxmox.com>
>
> This is explicitly allowed in the documentation and happens
> easily with cgroupv2 as there it is used to inherit from the
> closest ancestor.
>
> Signed-off-by: Wolfgang Bumiller <w.bumil...@proxmox.com>
> ---
> src/PVE/CpuSet.pm | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/src/PVE/CpuSet.pm b/src/PVE/CpuSet.pm
> index 297e995..a16f7ee 100644
> --- a/src/PVE/CpuSet.pm
> +++ b/src/PVE/CpuSet.pm
> @@ -40,9 +40,6 @@ sub new_from_path {
>
> my ($count, $members) = parse_cpuset($set_text);
>
> - die "got empty cpuset for cgroup '$path'\n"
> - if !$count;
> -
> return $class->new($members);
> }
>
> @@ -81,8 +78,6 @@ sub write_to_cgroup {
> $value .= $cpuid;
> }
>
> - die "unable to write empty cpu set\n" if !length($value);
> -
> open(my $fh, '>', $filename) || die "failed to open '$filename' - $!\n";
> PVE::Tools::safe_print($filename, $fh, "$value\n");
> close($fh) || die "failed to close '$filename' - $!\n";
>
applied both patches, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
