From: Rene Rebe <rene@exactcode.de>
To: sparclinux@vger.kernel.org
Subject: Re: Oops in tcp_sendmsg on T1000
Date: Sat, 08 Jul 2006 18:57:05 +0000 [thread overview]
Message-ID: <200607082057.05266.rene@exactcode.de> (raw)
In-Reply-To: <200607011421.56811.rene@exactcode.de>
Hi,
On Saturday 08 July 2006 03:21, David Miller wrote:
> From: Rene Rebe <rene@exactcode.de>
> Date: Sat, 1 Jul 2006 14:21:56 +0200
>
> > kernel BUG at include/linux/skbuff.h:457!
> > \|/ ____ \|/
> > "@'/ .. \`@"
> > /_| \__/ |_\
> > \__U_/
> > sshd(21849): Kernel bad sw trap 5 [#1]
> > TSTATE: 0000000011001601 TPC: 00000000005c5c2c TNPC: 00000000005c5c30 Y:
> > 00000000 Not tainted TPC: <tcp_sendmsg+0x3b0/0xcb0>
> > g0: 0000000000000830 g1: 0000000000656400 g2: 0000000000714400 g3:
> > 0000000000002bb9 g4: fffff8018cde7060 g5: fffff80003d660c0 g6:
> > fffff8016f6f0000 g7: 0000000000000000 o0: 000000000000002d o1:
> > 0000000000621e30 o2: 00000000000001c9 o3: 0000000000000240 o4:
> > 00000000ff1e8eef o5: 0000000000000240 sp: fffff8016f6f2fb1 ret_pc:
> > 00000000005c5c24 RPC: <tcp_sendmsg+0x3a8/0xcb0>
>
> Let's try to get some more debugging. It looks like an SKB is being
> referenced after it has been freed up, or something like this.
>
> Please add this patch and report what it prints, thanks a lot.
>
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index f6a2d92..a3cb2cf 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -467,6 +467,10 @@ static inline void skb_entail(struct soc
> TCP_SKB_CB(skb)->end_seq = tp->write_seq;
> TCP_SKB_CB(skb)->flags = TCPCB_FLAG_ACK;
> TCP_SKB_CB(skb)->sacked = 0;
> + if (skb->nohdr) {
> + printk("TCP DEBUG: Bogus skb->nohdr, word[%08x]\n",
> + *(&skb->priority + 1));
> + }
> skb_header_release(skb);
> __skb_queue_tail(&sk->sk_write_queue, skb);
> sk_charge_skb(sk, skb);
I run a 2.6.17.4 kernel with the above patch on the T1000, now.
But since I got the Oops only once so far it might take some days++
to reappear ...
--
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
http://exactcode.de | http://t2-project.org | http://rebe.name
+49 (0)30 / 255 897 45
next prev parent reply other threads:[~2006-07-08 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 12:21 Oops in tcp_sendmsg on T1000 Rene Rebe
2006-07-01 22:19 ` David Miller
2006-07-02 15:14 ` Rene Rebe
2006-07-02 16:32 ` David Miller
2006-07-02 17:35 ` Rene Rebe
2006-07-02 19:13 ` Jurij Smakov
2006-07-03 0:02 ` Dennis Gilmore
2006-07-03 16:16 ` Ben Collins
2006-07-03 16:22 ` Dennis Gilmore
2006-07-03 18:20 ` David Miller
2006-07-04 2:21 ` Jurij Smakov
2006-07-08 1:21 ` David Miller
2006-07-08 18:57 ` Rene Rebe [this message]
2006-07-08 20:49 ` David Miller
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=200607082057.05266.rene@exactcode.de \
--to=rene@exactcode.de \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.