| To: | george@xxxxxxxxxx |
|---|---|
| Subject: | Re: System crash in tcp_fragment() |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 20 May 2002 17:18:19 -0700 (PDT) |
| Cc: | kuznet@xxxxxxxxxxxxx, ak@xxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, ak@xxxxxx, pekkas@xxxxxxxxxx |
| In-reply-to: | <3CE99434.20E7479C@xxxxxxxxxx> |
| References: | <200205210011.EAA04286@xxxxxxxxxxxxx> <3CE99434.20E7479C@xxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
From: george anzinger <george@xxxxxxxxxx> Date: Mon, 20 May 2002 17:26:29 -0700 Ah, but we have. in_interrupt() was fixed about a month ago. I think Robert got it into all the patches. Whats more, it is a bit faster too :) Well, back to the main point, this code is pretty stable by any measurement. I truly believe it is some side effect of either a preemption gotcha or a driver bug. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: System crash in tcp_fragment(), george anzinger |
|---|---|
| Next by Date: | Re: System crash in tcp_fragment(), george anzinger |
| Previous by Thread: | Re: System crash in tcp_fragment(), george anzinger |
| Next by Thread: | Re: System crash in tcp_fragment(), Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |