Re: KERNEL: assertion (!sk->sk_forward

netdev

Re: KERNEL: assertion (!sk->sk_forward_alloc)

To:	Anton Blanchard <anton@xxxxxxxxx>
Subject:	Re: KERNEL: assertion (!sk->sk_forward_alloc)
From:	"David S. Miller" <davem@xxxxxxxxxxxxx>
Date:	Mon, 29 Nov 2004 17:22:10 -0800
Cc:	netdev@xxxxxxxxxxx
In-reply-to:	<20041129211855.GC17540@krispykreme.ozlabs.ibm.com>
References:	<20041129211855.GC17540@krispykreme.ozlabs.ibm.com>
Sender:	netdev-bounce@xxxxxxxxxxx

On Tue, 30 Nov 2004 08:18:57 +1100
Anton Blanchard <anton@xxxxxxxxx> wrote:

> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (180)
> 
> Note that this test was run using the send-to-self patch.

Try to reproduce without that patch installed.

If there is any mixup of SKB handling by any element in the
path the packet travels, you're screw up all the TCP
accounting knobs on the socket and easily trigger messages
like the above.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
KERNEL: assertion (!sk->sk_forward_alloc), Anton Blanchard Re: KERNEL: assertion (!sk->sk_forward_alloc), David S. Miller <=

Previous by Date:	Re: odd behavior with r8169 and pcap, Francois Romieu
Next by Date:	Re: via-rhine unable to send back-to-back packets?, David S. Miller
Previous by Thread:	KERNEL: assertion (!sk->sk_forward_alloc), Anton Blanchard
Next by Thread:	Re: odd behavior with r8169 and pcap, Terry Griffin
Indexes:	[Date] [Thread] [Top] [All Lists]