# Re: \[PATCH 01/12\] netvm: Prevent a stream-specific deadlock - From: David Miller \ - Date: 2012-05-11 05:11:53 - List: netdev - Page: https://ratatoskr.run/netdev/2012/05/3862491 - Thread: https://ratatoskr.run/linux-mm/2012/05/3861977/t.md ```text From: Mel Gorman Date: Thu, 10 May 2012 14:54:14 +0100 > It could happen that all !SOCK_MEMALLOC sockets have buffered so > much data that we're over the global rmem limit. This will prevent > SOCK_MEMALLOC buffers from receiving data, which will prevent userspace > from running, which is needed to reduce the buffered data. > > Fix this by exempting the SOCK_MEMALLOC sockets from the rmem limit. > > Signed-off-by: Peter Zijlstra > Signed-off-by: Mel Gorman This introduces an invariant which I am not so sure is enforced. With this change it is absolutely required that once a socket becomes SOCK_MEMALLOC it must never _ever_ lose that attribute. Otherwise we can end up liberating global rmem tokens which we never actually took. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org ```