From: Brian Davids <dlister@yossman.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-bk multiple oops on boot
Date: Sun, 16 Mar 2003 20:09:35 -0500 [thread overview]
Message-ID: <3E75204F.1070603@yossman.net> (raw)
In-Reply-To: <20030316163444.4d495d59.akpm@digeo.com>
Andrew Morton wrote:
> 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 */
That fixed it for me... thanks!
Brian Davids
prev parent reply other threads:[~2003-03-17 0:58 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
2003-03-17 1:09 ` Brian Davids [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=3E75204F.1070603@yossman.net \
--to=dlister@yossman.net \
--cc=akpm@digeo.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