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@xxxxxxxxxx> > --- > 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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
