Kir Kolyshkin 1880d2fc05 libct/cg/fs/memory: handle EBUSY ...

EBUSY when trying to set memory limit may mean the new limit is too low
(lower than the current usage, and the kernel can't do anything).
Provide a more specific error for such case.

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

2021-02-23 16:11:55 -08:00

..

devices

libcontainer/devices: remove "Device" prefix from types

2020-12-01 11:11:23 +01:00

ebpf

ebpf: fix device access check

2021-02-07 19:33:10 +01:00

fs

libct/cg/fs/memory: handle EBUSY

2021-02-23 16:11:55 -08:00

fs2

Fix memory stats for cache in fs2

2021-02-22 12:27:12 +01:00

fscommon

Implement GetStat for cpuset cgroup.

2021-01-19 18:02:11 +01:00

systemd

libct/cgroups/systemd: don't set limits in Apply

2021-02-19 18:53:24 -08: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

libct/cgroups/utils: move cgroup v1 code to separate file

2020-06-16 12:45:07 -07:00

stats.go

Implement GetStat for cpuset cgroup.

2021-01-19 18:02:11 +01:00

utils_test.go

merge branch 'pr-2599'

2021-02-01 11:04:11 +11:00

utils.go

libct/cg/utils: silence a linter warning

2020-12-03 10:24:27 -08:00

v1_utils.go

libct/cgroups/v1_utils: implement mountinfo cache

2021-01-06 14:54:22 -08:00