public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
To: William Dauchy <william-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ps stuck on cmdline reading
Date: Tue, 3 Feb 2015 20:40:36 +0100	[thread overview]
Message-ID: <20150203194036.GA2490@dhcp22.suse.cz> (raw)
In-Reply-To: <20150121095808.GA18656-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org>

On Wed 21-01-15 10:58:08, William Dauchy wrote:
> 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.

What does /proc/<ps pid>/stack say?

-- 
Michal Hocko
SUSE Labs

  parent reply	other threads:[~2015-02-03 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  9:58 ps stuck on cmdline reading William Dauchy
     [not found] ` <20150121095808.GA18656-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org>
2015-02-03 19:40   ` Michal Hocko [this message]
     [not found]     ` <20150203194036.GA2490-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-02-05 15:22       ` William Dauchy
     [not found]         ` <20150205152233.GI3008-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org>
2015-02-05 15:45           ` Michal Hocko
     [not found]             ` <20150205154558.GF19104-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-02-10 15:10               ` William Dauchy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150203194036.GA2490@dhcp22.suse.cz \
    --to=mhocko-alswssmvlrq@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=william-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox