Kir Kolyshkin 568cd62fa1 cgroupv2: only treat -1 as "max" ...

Commit 6905b72154 treats all negative values as "max",
citing cgroup v1 compatibility as a reason. In fact, in
cgroup v1 only -1 is treated as "unlimited", and other
negative values usually calse an error.

Treat -1 as "max", pass other negative values as is
(the error will be returned from the kernel).

Fixes: 6905b72154
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

2020-04-08 04:08:49 -07:00

..

ebpf

cgroup2: ebpf: increase RLIM_MEMLOCK to avoid BPF_PROG_LOAD error

2019-11-07 15:43:27 +09:00

fs

libcontainer: use errors.Is() and errors.As()

2020-04-02 20:34:01 -07:00

fs2

cgroupv2: only treat -1 as "max"

2020-04-08 04:08:49 -07:00

fscommon

Revert "Merge pull request #2280 from kolyshkin/errors-unwrap"

2020-04-02 19:41:11 -07:00

systemd

Remove unused consts testScopeWait and testSliceWait

2020-04-03 21:09:43 +02:00

cgroups_test.go

.travis.yml: add Fedora 31 vagrant box (for cgroup2)

2019-10-31 16:53:01 +09:00

cgroups_unsupported.go

Move libcontainer into subdirectory

2015-06-21 19:29:15 -07:00

cgroups.go

libcontainer: add method to get cgroup config from cgroup Manager

2019-12-17 22:46:03 +00:00

stats.go

Expose memory.use_hierarchy in MemoryStats

2017-03-31 13:40:34 -04:00

utils_test.go

cgroup2: add CpuMax conversion

2020-03-13 02:58:39 +09:00

utils.go

libcontainer: use errors.Is() and errors.As()

2020-04-02 20:34:01 -07:00