From: Linux Geek <bourne@ToughGuy.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [DUMB]: Is kernel oops always a kernel bug ???
Date: Fri, 17 Jan 2003 11:33:46 +0530 [thread overview]
Message-ID: <3E279CC2.9040806@ToughGuy.net> (raw)
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 ?
TIA
next reply other threads:[~2003-01-17 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 6:03 Linux Geek [this message]
2003-01-17 6:14 ` [DUMB]: Is kernel oops always a kernel bug ??? Jurriaan
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=3E279CC2.9040806@ToughGuy.net \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.