From: Russell King <rmk@arm.linux.org.uk>
To: devik@server.cdi.cz (Devik)
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: test12 oops with NF+ping -s 1500
Date: Thu, 14 Dec 2000 13:03:04 +0000 (GMT) [thread overview]
Message-ID: <200012141303.eBED34106174@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10012131543350.16650-300000@luxik.cdi.cz> from "Devik" at Dec 13, 2000 03:56:42 PM
Devik writes:
> I just tried to narrow problem with DFE530 card and found
> another (rather fatal) bug in 2.4.0-test12.
> I attached both my config and ksymoops output. It seems
> that ip_defrag is called with skb where skb->dev is NULL.
> It then crashes in ip_queue_frag.
> I can trigger it regulary by ping -s 1500 some_ip (to
> ping thru ethernet iff) on two computers.
> Please cc me in replies to devik@cdi.cz.
Linus,
How about we kill these recursive oopsen by changing the
printk("Aiee, killing interrupt handler") to a panic? If we're
entering do_exit() from an interrupt, we will eventually enter
schedule(), again as an interrupt, which will BUG(), and then
we'll repeat ad-infinitum.
panic() is better since we break this fatal recursive oops loop,
and we also get the additional advantage that a machine with
"panic=60" set will recover.
Currently, you hit this recursive oops problem, and its game over
until reset (unless you have a hardware watchdog).
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-14 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 14:56 Devik
2000-12-14 13:03 ` Russell King [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=200012141303.eBED34106174@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=devik@server.cdi.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®