[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+2_TiZ3dECAW8LV-Es=BjHCwgWw69zbWkr73at+0_c-EaDHmA@mail.gmail.com>
Date: Tue, 14 May 2013 11:29:46 +0800
From: Neil Zhang <glacier1980@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: raulxiong@...il.com, Robert Love <rlove@...gle.com>,
Shankar Brahadeeswaran <shankoo77@...il.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
LKML <linux-kernel@...r.kernel.org>,
Bjorn Bringert <bringert@...gle.com>,
devel <devel@...verdev.osuosl.org>,
Hugh Dickins <hughd@...gle.com>,
Anjana V Kumar <anjanavk12@...il.com>,
Dad <akpm@...ux-foundation.org>,
linux-next <linux-next@...r.kernel.org>
Subject: Re: [PATCH -next] ashmem: Fix ashmem_shrink deadlock.
2013/5/14 Greg Kroah-Hartman <gregkh@...uxfoundation.org>:
> On Wed, May 01, 2013 at 09:56:13AM -0400, Robert Love 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>
>> ---
>> drivers/staging/android/ashmem.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> Based on Andrew's review comments, I'll drop this from my queue and wait
> for a "better" fix for this.
>
> 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/
We found the similar issue these days.
Add RaulXiong to paste the call stack.
Best Regards,
Neil Zhang
--
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