From: William Dauchy <william-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org>
To: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
Cc: William Dauchy <william-M8Sm6a3kpgNeoWH0uzbU5w@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Trond Myklebust
<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
Anna Schumaker
<Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Subject: Re: ps stuck on cmdline reading
Date: Tue, 10 Feb 2015 16:10:50 +0100 [thread overview]
Message-ID: <20150210151050.GB17444@gandi.net> (raw)
In-Reply-To: <20150205154558.GF19104-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Feb05 16:45, Michal Hocko wrote:
> OK, so the memcg reclaim gets down to nfs and it wants to evict its
> inode and that is waiting for the page to get unlocked. It would be
> interesting to find out who is keeping the page locked. What is the nfsd
> doing?
Trond points me the commit
9590544 NFS: avoid deadlocks with loop-back mounted NFS filesystems.
but it relies on sched commit as well, it seems hard to be backported in
3.14.x
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-02-10 15:10 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
[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 [this message]
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=20150210151050.GB17444@gandi.net \
--to=william-m8sm6a3kpgneowh0uzbu5w@public.gmane.org \
--cc=Anna.Schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@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