On Fri, Mar 24, 2017 at 06:05:45PM +0300, Andrey Ryabinin wrote: > Just fix the drm code. There is zero point in releasing memory under spinlock. I disagree. The spinlock has to be held while deleting from the hash table. Sure, we could change the API to return the object removed, and then force the caller to free the object that was removed from the hash table outside the lock it's holding, but that's a really inelegant API. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
