From: David Rientjes <rientjes@google.com>
To: Robert Love <rlove@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Shankar Brahadeeswaran <shankoo77@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Bringert <bringert@google.com>,
devel <devel@driverdev.osuosl.org>,
Hugh Dickins <hughd@google.com>,
Anjana V Kumar <anjanavk12@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [PATCH -next] ashmem: Fix ashmem_shrink deadlock.
Date: Thu, 2 May 2013 11:22:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1305021121160.2493@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305010853450.4547@chino.kir.corp.google.com>
On Wed, 1 May 2013, David Rientjes wrote:
> > Don't acquire ashmem_mutex in ashmem_shrink if we've somehow recursed into the
> > shrinker code from within ashmem. Just bail out, avoiding a deadlock. This is
> > fine, as ashmem cache pruning is advisory anyhow.
> >
> > Signed-off-by: Robert Love <rlove@google.com>
>
> Any reason not to send this to stable@vger.kernel.org if it fixes an
> observable deadlock? (It's annotated to be applied to linux-next, but I
> don't see any differences between it and Linus's tree.)
>
This was sent separately to stable@vger.kernel.org before being merged
into Linus's tree . Greg, could this be queued up for 3.10 with a cc to
stable@vger.kernel.org?
next prev parent reply other threads:[~2013-05-02 18:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 13:56 [PATCH -next] ashmem: Fix ashmem_shrink deadlock Robert Love
2013-05-01 15:54 ` David Rientjes
2013-05-02 18:22 ` David Rientjes [this message]
2013-05-02 20:39 ` Greg Kroah-Hartman
2013-05-07 20:52 ` Andrew Morton
2013-05-13 21:42 ` Greg Kroah-Hartman
2013-05-14 3:29 ` Neil Zhang
2013-05-14 3:37 ` Raul Xiong
2013-05-16 8:15 ` Raul Xiong
2013-05-16 13:44 ` Robert Love
2013-05-16 16:45 ` Andrew Morton
2013-05-16 17:08 ` Robert Love
2013-05-16 17:19 ` Andrew Morton
2013-05-16 17:28 ` Robert Love
2013-09-17 5:05 ` Raul Xiong
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=alpine.DEB.2.02.1305021121160.2493@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=anjanavk12@gmail.com \
--cc=bringert@google.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rlove@google.com \
--cc=shankoo77@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).