From: Jurriaan <thunder7@xs4all.nl>
To: Linux Geek <bourne@ToughGuy.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [DUMB]: Is kernel oops always a kernel bug ???
Date: Fri, 17 Jan 2003 07:14:58 +0100 [thread overview]
Message-ID: <20030117061458.GA3450@middle.of.nowhere> (raw)
In-Reply-To: <3E279CC2.9040806@ToughGuy.net>
From: Linux Geek <bourne@ToughGuy.net>
Date: Fri, Jan 17, 2003 at 11:33:46AM +0530
> Hi all ,
>
> If a kernel oops, then is the problem always with the kernel ? Can't a
> user proggie ( running as root ) do something insane and make the
> kernel oops ?
>
That shouldn't happen - it's called DOS (Denial-Of-Service) if a user
program can make the kernel oops. Some of these probably still exist in
the linux kernel, nothing is perfect :-)
But another option exists: hardware failures. If your memory decides to
take a break, you will get an oops also.
Good luck,
Jurriaan
--
Holed up in your little room, we talk for hour on empty hour,
pacing up and down between the walls that we have built ourselves.
New Model Army - Long Goodbye
GNU/Linux 2.5.58 SMP/ReiserFS 2x2752 bogomips load av: 0.16 0.61 0.61
next prev parent reply other threads:[~2003-01-17 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 6:03 [DUMB]: Is kernel oops always a kernel bug ??? Linux Geek
2003-01-17 6:14 ` Jurriaan [this message]
2003-01-17 6:18 ` Valdis.Kletnieks
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=20030117061458.GA3450@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=bourne@ToughGuy.net \
--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