From: Anton Blanchard <anton@samba.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: KERNEL: assertion (!sk->sk_forward_alloc)
Date: Sun, 5 Dec 2004 18:46:58 +1100 [thread overview]
Message-ID: <20041205074658.GA19168@krispykreme.ozlabs.ibm.com> (raw)
In-Reply-To: <20041129172210.687bcad3.davem@davemloft.net>
Hi Dave,
> 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.
I'll try. FYI we have 70 gigabit cards in that machine, the reason
send-to-self is so useful is that we only need one expensive machine.
Without the patch we need to find two expensive machines with 35
gigabits in each :)
Anton
prev parent reply other threads:[~2004-12-05 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 21:18 KERNEL: assertion (!sk->sk_forward_alloc) Anton Blanchard
2004-11-30 1:22 ` David S. Miller
2004-12-05 7:46 ` Anton Blanchard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041205074658.GA19168@krispykreme.ozlabs.ibm.com \
--to=anton@samba.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).