Re: Deadlock in 2.2 sock_alloc_send_skb?

[Andi Kleen]

On Thu, May 10, 2001 at 01:57:49PM +0100, Alan Cox wrote:
> > If that happens, and the socket uses GFP_ATOMIC allocation, the while (1)
> > loop in sock_alloc_send_skb() will endlessly spin, without ever calling
> > schedule(), and all the time holding the kernel lock ...
> 
> If the socket is using GFP_ATOMIC allocation it should never loop. That is
> -not-allowed-. 

It is just not clear why any socket should use GFP_ATOMIC. I can understand
it using GFP_BUFFER e.g. for nbd, but GFP_ATOMIC seems to be rather radical
and fragile.

-Andi