Nadeshiko Manju
Nadeshiko Manju
There is two LGTM from the people who have the write access to this repo. Do we need more LGTM?
I think this maybe make sense. For now, we use `/proc/meminfo` to calculate the swap info, and `memory.stat` to calculate the usage info. I think this may be strange. Perhaps...
ping @lifubang @AkihiroSuda (
@AkihiroSuda Would you mind to retry the test for me? some of them failed because of the APT apt throttled
```text E: Failed to fetch https://download.opensuse.org/repositories/devel:/tools:/criu/xUbuntu_22.04/amd64/criu_3.18-1_amd64.deb Redirection from https to 'http://provo-mirror.opensuse.org/repositories/devel%3A/tools%3A/criu/xUbuntu_22.04/amd64/criu_3.18-1_amd64.deb' is forbidden [IP: 195.135.223.226 443] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?...
@AkihiroSuda ping for review（
> Looking at the diff: > > [v1.1.7...v1.1.8](https://github.com/opencontainers/runc/compare/v1.1.7...v1.1.8) > > My initial suspect would be this PR; > > * [Backport riscv64 support into 1.1.x #3905](https://github.com/opencontainers/runc/pull/3905) > > There's not...
> I'm not sure if there's a nice way to detect whether the libc we're using supports `--static-pie` other than doing the build (which would be quite ugly to do...
I think maybe we have two issues to solve before supporting SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV 1. libsescomp need a stable release 2. How to test the SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV?
About the test, I may have some ideas. 1. we may need a new binary for SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV in contrib/cmd/, like old seccompagent 2. we can listen to UDS to reach...