Messages in this thread | | | Date | Thu, 10 May 2001 19:30:47 +0200 | From | Andi Kleen <> | Subject | Re: Deadlock in 2.2 sock_alloc_send_skb? |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |