On Wed, 1 May 2013, 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 <[email protected]>
Any reason not to send this to [email protected] 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.) _______________________________________________ devel mailing list [email protected] http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
