From: "Dan Aizenstros" <daizenstros@quicklogic.com>
To: <linux-mips@oss.sgi.com>
Subject: Oops in do_mounts.c file.
Date: Fri, 04 Jan 2002 12:57:00 -0800 [thread overview]
Message-ID: <sc35a6be.092@quicklogic.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Hello all,
I am getting an oops in the mount_root function if I
pass root=/dev/nfs to my 2.5.1 kernel.
I am also getting an oops in the mount_block_root
function if I pass root=/dev/hda3 to my 2.5.1 kernel.
The problem appears to be related to the following two
lines in the init/do_mounts.c file:
static char * __initdata root_mount_data;
static char * __initdata root_fs_names;
The __initdata macro appears to be incorrectly used.
In include/linux/init.h the explanation for the macro
says the __initdata should appear after the variable
name. It also indicates that the variable shoud be
initialized.
The attached patch fixes the problem.
-- Dan A.
[-- Attachment #2: do_mounts.patch --]
[-- Type: application/octet-stream, Size: 658 bytes --]
Index: do_mounts.c
===================================================================
RCS file: /cvs/linux/init/do_mounts.c,v
retrieving revision 1.1
diff -u -r1.1 do_mounts.c
--- do_mounts.c 2001/12/19 00:04:01 1.1
+++ do_mounts.c 2002/01/04 22:02:20
@@ -239,14 +239,14 @@
__setup("root=", root_dev_setup);
-static char * __initdata root_mount_data;
+static char * root_mount_data __initdata = NULL;
static int __init root_data_setup(char *str)
{
root_mount_data = str;
return 1;
}
-static char * __initdata root_fs_names;
+static char * root_fs_names __initdata = NULL;
static int __init fs_names_setup(char *str)
{
root_fs_names = str;
WARNING: multiple messages have this Message-ID (diff)
From: "Dan Aizenstros" <daizenstros@quicklogic.com>
To: linux-mips@oss.sgi.com
Subject: Oops in do_mounts.c file.
Date: Fri, 04 Jan 2002 12:57:00 -0800 [thread overview]
Message-ID: <sc35a6be.092@quicklogic.com> (raw)
Message-ID: <20020104205700.eS-XMXVxn6rlo6BVsKMFMGabecIUyRgVTJmeG1ZnPZg@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Hello all,
I am getting an oops in the mount_root function if I
pass root=/dev/nfs to my 2.5.1 kernel.
I am also getting an oops in the mount_block_root
function if I pass root=/dev/hda3 to my 2.5.1 kernel.
The problem appears to be related to the following two
lines in the init/do_mounts.c file:
static char * __initdata root_mount_data;
static char * __initdata root_fs_names;
The __initdata macro appears to be incorrectly used.
In include/linux/init.h the explanation for the macro
says the __initdata should appear after the variable
name. It also indicates that the variable shoud be
initialized.
The attached patch fixes the problem.
-- Dan A.
[-- Attachment #2: do_mounts.patch --]
[-- Type: application/octet-stream, Size: 658 bytes --]
Index: do_mounts.c
===================================================================
RCS file: /cvs/linux/init/do_mounts.c,v
retrieving revision 1.1
diff -u -r1.1 do_mounts.c
--- do_mounts.c 2001/12/19 00:04:01 1.1
+++ do_mounts.c 2002/01/04 22:02:20
@@ -239,14 +239,14 @@
__setup("root=", root_dev_setup);
-static char * __initdata root_mount_data;
+static char * root_mount_data __initdata = NULL;
static int __init root_data_setup(char *str)
{
root_mount_data = str;
return 1;
}
-static char * __initdata root_fs_names;
+static char * root_fs_names __initdata = NULL;
static int __init fs_names_setup(char *str)
{
root_fs_names = str;
next reply other threads:[~2002-01-04 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:57 Dan Aizenstros [this message]
2002-01-04 20:57 ` Oops in do_mounts.c file Dan Aizenstros
2002-01-07 1:15 ` Ralf Baechle
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=sc35a6be.092@quicklogic.com \
--to=daizenstros@quicklogic.com \
--cc=linux-mips@oss.sgi.com \
/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