From: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: + mm-memcg-lockdep-annotation-for-memcg-oom-lock.patch added to -mm tree
Date: Thu, 31 Oct 2013 10:37:58 -0400 [thread overview]
Message-ID: <20131031143758.GE14054@cmpxchg.org> (raw)
In-Reply-To: <20131031085017.GB13144@dhcp22.suse.cz>
On Thu, Oct 31, 2013 at 09:50:17AM +0100, Michal Hocko wrote:
> On Wed 30-10-13 15:12:48, Andrew Morton wrote:
> > Subject: + mm-memcg-lockdep-annotation-for-memcg-oom-lock.patch added to -mm tree
> > To: hannes@cmpxchg.org,mhocko@suse.cz
> > From: akpm@linux-foundation.org
> > Date: Wed, 30 Oct 2013 15:12:48 -0700
> >
> >
> > The patch titled
> > Subject: mm: memcg: lockdep annotation for memcg OOM lock
> > has been added to the -mm tree. Its filename is
> > mm-memcg-lockdep-annotation-for-memcg-oom-lock.patch
> >
> > This patch should soon appear at
> > http://ozlabs.org/~akpm/mmots/broken-out/mm-memcg-lockdep-annotation-for-memcg-oom-lock.patch
> > and later at
> > http://ozlabs.org/~akpm/mmotm/broken-out/mm-memcg-lockdep-annotation-for-memcg-oom-lock.patch
> >
> > Before you just go and hit "reply", please:
> > a) Consider who else should be cc'ed
> > b) Prefer to cc a suitable mailing list as well
> > c) Ideally: find the original patch on the mailing list and do a
> > reply-to-all to that, adding suitable additional cc's
> >
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> >
> > The -mm tree is included into linux-next and is updated
> > there every 3-4 working days
> >
> > ------------------------------------------------------
> > From: Johannes Weiner <hannes@cmpxchg.org>
> > Subject: mm: memcg: lockdep annotation for memcg OOM lock
> >
> > The memcg OOM lock is a mutex-type lock that is open-coded due to memcg's
> > special needs. Add annotations for lockdep coverage.
>
> I am not sure what this gives us to be honest. AA and AB-BA deadlocks
> are impossible due to nature of the lock (it is trylock so we never
> block on it).
It's not an actual trylock, because we loop around it. If it fails,
we wait for the unlock, restart the fault, and try again. That's a
LOCK operation.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-11-01 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52718460.4+rPcYBdFtC2v3uh%akpm@linux-foundation.org>
2013-10-31 8:50 ` Michal Hocko
2013-10-31 14:37 ` Johannes Weiner [this message]
2013-10-31 15:36 ` Michal Hocko
2013-10-31 16:28 ` Johannes Weiner
2013-10-31 16:39 ` Michal Hocko
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=20131031143758.GE14054@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.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