To the TCP maintainer: It appears that tcp.c:1029 is ignoring sk->allocation, as all the call to tcp_alloc_skb() has GFP_KERNEL hardcoded. We are developing modules that use TCP/IP, and therefore set sk->allocation to GFP_ATOMIC. With this value getting ignored in tcp.c, the kernel eventually hangs when there is no available memory. Please let us know if this is indeed a bug (rather than an our improper us of sk->allocation) and if so whether or not it will be addressed in the first official release of 2.4. Best regards, -- Mike Mesnier Storage Architecture/ Enterprise Architecture Laboratory - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
