From: Andrew Morton <akpm@digeo.com>
To: Brian Davids <dlister@yossman.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-bk multiple oops on boot
Date: Sun, 16 Mar 2003 16:34:44 -0800 [thread overview]
Message-ID: <20030316163444.4d495d59.akpm@digeo.com> (raw)
In-Reply-To: <3E75138C.7030607@yossman.net>
Brian Davids <dlister@yossman.net> wrote:
>
> I get the following oopsen during booting with 2.5.64-bk pulled at
> around 10 AM EST today... system is running RedHat Phoebe 8.0.94 beta,
> gcc 3.2.1
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> c01a4c9b
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0060:[<c01a4c9b>] Not tainted
> EFLAGS: 00010283
> EIP is at devfs_get_ops+0xb/0x40
Does this help?
diff -puN fs/devfs/base.c~devfs-oops-fix fs/devfs/base.c
--- 25/fs/devfs/base.c~devfs-oops-fix 2003-03-16 16:33:16.000000000 -0800
+++ 25-akpm/fs/devfs/base.c 2003-03-16 16:33:49.000000000 -0800
@@ -1802,8 +1802,11 @@ int devfs_generate_path (devfs_handle_t
static struct file_operations *devfs_get_ops (devfs_handle_t de)
{
struct file_operations *ops = de->u.cdev.ops;
- struct module *owner = ops->owner;
+ struct module *owner;
+ if (!ops)
+ return NULL;
+ owner = ops->owner;
read_lock (&de->parent->u.dir.lock); /* Prevent module from unloading */
if ( (de->next == de) || !try_module_get (owner) )
{ /* Entry is already unhooked or module is unloading */
_
next prev parent reply other threads:[~2003-03-17 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 0:15 2.5.64-bk multiple oops on boot Brian Davids
2003-03-17 0:34 ` Andrew Morton [this message]
2003-03-17 1:09 ` Brian Davids
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=20030316163444.4d495d59.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=dlister@yossman.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