| To: | george@xxxxxxxxxx |
|---|---|
| Subject: | Re: System crash in tcp_fragment() |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 20 May 2002 15:08:33 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, ak@xxxxxx, kuznet@xxxxxxxxxxxxx, pekkas@xxxxxxxxxx |
| In-reply-to: | <3CE95190.75C52E2D@xxxxxxxxxx> |
| References: | <3CE95190.75C52E2D@xxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
From: george anzinger <george@xxxxxxxxxx> Date: Mon, 20 May 2002 12:42:08 -0700 I wonder if you could help me squash a bug in the tcp code. Here is what we know thus far: An SMP (x386 dual) 2.4.17 kernel crashes with an attempt to deference NULL at the end of tcp_fragment() (in net/ipv4/tcp_output.c) while attempting to link in the newly created fragment. The bugzilla report is: %99 of all such bug reports turn out to be driver bugs where the net driver frees SKBs improperly or there is some missing internal locking in the net device driver. I think you efforts are better spent auditing what net drivers are being used on this machine :-) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: System crash in tcp_fragment(), kuznet |
|---|---|
| Next by Date: | Re: System crash in tcp_fragment(), george anzinger |
| Previous by Thread: | Re: System crash in tcp_fragment(), Andi Kleen |
| Next by Thread: | [PATCH] RFC save a few atomics in tcp_memory_schedule(), Nivedita Singhvi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |