netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Andi Kleen <ak@muc.de>
Cc: "David S. Miller" <davem@redhat.com>,
	kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
	linux-net@vger.kernel.org, pekkas@netcore.fi,
	andrew.r.cress@intel.com
Subject: Re: Network oops
Date: Fri, 28 Jun 2002 12:56:31 -0700	[thread overview]
Message-ID: <afif9f$oe1$2@main.gmane.org> (raw)
In-Reply-To: 20020622025551.A1919@averell

We finally found the problem.  I want to thank the folks who
gave any thought and/or feedback to us, particularly Alexey
and David.

For what its worth we tracked it down to the kernel memory
allocation routines allocating the same buffer to two
different network requesters.  This in turn was caused by a
basic flaw in the preemption code that preempted on
spin_unlock, REGARDLESS OF THE STATE OF THE INTERRUPT
SYSTEM.
-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Real time sched:  http://sourceforge.net/projects/rtsched/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

  parent reply	other threads:[~2002-06-28 19:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3CE95190.75C52E2D@mvista.com>
2002-05-20 20:29 ` System crash in tcp_fragment() Andi Kleen
     [not found] ` <20020520222937.A1467@averell>
2002-05-20 21:18   ` george anzinger
2002-05-20 21:25 ` kuznet
2002-05-20 22:08 ` David S. Miller
     [not found] ` <200205202125.BAA03545@sex.inr.ac.ru>
2002-05-20 23:01   ` george anzinger
2002-05-20 23:54   ` Andi Kleen
2002-06-09 17:31   ` Network oops george anzinger
     [not found]   ` <3D0390E2.1B80ADEE@mvista.com>
2002-06-10  4:31     ` David S. Miller
2002-06-10  4:32     ` David S. Miller
     [not found]     ` <20020609.213150.32126725.davem@redhat.com>
2002-06-10  4:48       ` george anzinger
     [not found]       ` <3D042F8F.72764243@mvista.com>
2002-06-10  5:06         ` David S. Miller
2002-06-20 17:19         ` george anzinger
     [not found]         ` <3D120EAE.5A0D365E@mvista.com>
2002-06-21  0:38           ` David S. Miller
     [not found]           ` <20020620.173805.55219901.davem@redhat.com>
2002-06-21 14:16             ` george anzinger
     [not found]             ` <3D133538.60B6810C@mvista.com>
2002-06-21 14:17               ` David S. Miller
     [not found]               ` <20020621.071720.07439917.davem@redhat.com>
2002-06-21 15:12                 ` george anzinger
2002-06-22  0:55               ` Andi Kleen
     [not found]               ` <20020622025551.A1919@averell>
2002-06-28 19:56                 ` george anzinger [this message]
     [not found]     ` <20020609.213224.01016187.davem@redhat.com>
2002-06-10  8:11       ` george anzinger
     [not found]       ` <3D045F15.578E1DA9@mvista.com>
2002-06-10  8:31         ` David S. Miller
     [not found]         ` <20020610.013110.81671593.davem@redhat.com>
2002-06-10 14:12           ` george anzinger
2002-06-10 14:42 Mala Anand
2002-06-12  1:35 ` Donald Becker
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12 16:58 Mala Anand
     [not found] <OF8ADD9FF7.49EC72C0-ON85256BD6.005CEBAC@raleigh.ibm.com>
2002-06-12 17:42 ` Nivedita Singhvi

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='afif9f$oe1$2@main.gmane.org' \
    --to=george@mvista.com \
    --cc=ak@muc.de \
    --cc=andrew.r.cress@intel.com \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=pekkas@netcore.fi \
    /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).