ls-ggg d7a29a3b33 libct: clean cached rlimit nofile in go runtime ...

As reported in issue #4195, the new version(since 1.19) of go runtime
will cache rlimit-nofile. Before executing execve, the rlimit-nofile
of the process will be restored with the cache. In runc, this will
cause the rlimit-nofile set by the parent process for the container
to become invalid. It can be solved by clearing the cache.

Signed-off-by: ls-ggg <335814617@qq.com>
(cherry picked from commit f9f8abf310)
Signed-off-by: lifubang <lifubang@acmcoder.com>
(cherry picked from commit da68c8e37b)
Signed-off-by: lifubang <lifubang@acmcoder.com>

2024-05-17 18:18:29 +08:00

..

linux.go

deprecate libct.system.Execv

2024-05-16 21:47:26 +08:00

proc_test.go

libct/system.Stat: fix/improve/speedup

2021-08-19 19:48:39 -07:00

proc.go

Remove io/ioutil use

2021-10-14 13:46:02 -07:00

rlimit_go119.go

libct: clean cached rlimit nofile in go runtime

2024-05-17 18:18:29 +08:00

rlimit_stub.go

libct: clean cached rlimit nofile in go runtime

2024-05-17 18:18:29 +08:00

syscall_linux_32.go

*: add go-1.17+ go:build tags

2021-08-30 20:58:22 -07:00

syscall_linux_64.go

*: add go-1.17+ go:build tags

2021-08-30 20:58:22 -07:00