[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130502203935.GA25567@kroah.com>
Date: Thu, 2 May 2013 13:39:35 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Robert Love <rlove@...gle.com>, devel <devel@...verdev.osuosl.org>,
Shankar Brahadeeswaran <shankoo77@...il.com>,
Bjorn Bringert <bringert@...gle.com>,
Hugh Dickins <hughd@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-next <linux-next@...r.kernel.org>,
Anjana V Kumar <anjanavk12@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH -next] ashmem: Fix ashmem_shrink deadlock.
On Thu, May 02, 2013 at 11:22:18AM -0700, David Rientjes wrote:
> 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@...gle.com>
> >
> > Any reason not to send this to stable@...r.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@...r.kernel.org before being merged
> into Linus's tree . Greg, could this be queued up for 3.10 with a cc to
> stable@...r.kernel.org?
Yes, I'll handle all of this properly, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists