Hello, I am sometines triggering an issue on a v3.14.x (v3.14.18 here) where the `ps auxwwf` is stuck. The setup is several containers which own several process and with memory limit on each cgroup. A strace reveals the `ps` command is stuck on a read of a cmdline file. The concerned process itself is on a non-interruptible IO state. The ps command is executed in the global cgroup. I also had a similar issue on a 3.10.x some months ago where ps was stuck; the reason was the memory limit of the cgroup was reached and I only had to add some pages available to the conatiner in order to unlock the ps command. But in my case the cgroups which own the pid has still lots of memory available and I did not found a way to unlock the process. I don't know how to reproduce the issue but I am sometimes triggering it. Does someone has some hint? How can I get more debug info about it? Thanks, -- William
Attachment:
signature.asc
Description: Digital signature
