From: devnetfs <devnetfs@yahoo.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: question on panic()?
Date: Wed, 30 Jul 2003 04:11:25 -0700 (PDT) [thread overview]
Message-ID: <20030730111125.3876.qmail@web20413.mail.yahoo.com> (raw)
Hello,
I am writing a module and want to truly panic the machine in case
of critical errors. I used the panic() function. But after
panic() is called and panic() does its job, I am still able
to ping to this box from outside.
Looking at the panic() function, it looks all cpus _except_
the one on which panic() got called are halted ("hlt"). and
interrupts are reenabled on _this_ CPU, hence NIC interrupts
are allowed and pkts sent out in response to ping.
Why is this done? should'nt panic() halt all the CPUs?
And is there any way to halt all cpus? (can't do that after
called panic() as its NORET!). I am working on RH 2.4.X kernel.
(AFAIK this has not changed in 2.5 too).
Thanks in Advance,
A.
PS: please Cc: me the reply. I am not subscribed to lkml.
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
reply other threads:[~2003-07-30 11:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030730111125.3876.qmail@web20413.mail.yahoo.com \
--to=devnetfs@yahoo.com \
--cc=linux-kernel@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 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).