linux-mips
[Top] [All Lists]

Re: Oops in do_mounts.c file.

To: Dan Aizenstros <daizenstros@quicklogic.com>
Subject: Re: Oops in do_mounts.c file.
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Sun, 6 Jan 2002 23:15:28 -0200
Cc: linux-mips@oss.sgi.com
In-reply-to: <sc35a6be.092@quicklogic.com>; from daizenstros@quicklogic.com on Fri, Jan 04, 2002 at 12:57:00PM -0800
References: <sc35a6be.092@quicklogic.com>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Fri, Jan 04, 2002 at 12:57:00PM -0800, Dan Aizenstros wrote:

> 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.

Old gcc was more restrictive about the position of __attribute__() than
current gccs.  The comment documents older gcc.  Old in this context
means older than egcs 1.1.2 which is currently the required minmum version
to compile the kernel.

> The attached patch fixes the problem.

And that's highly suspect.  No matter with or without your patch
root_mount_data and root_fs_names should endup in .data.init.  So if your
patch indeed has an effect that your compiler seems is suspect.

Can you try to look at the generated assembler source and object files and
check into which sections gcc places these variables?

  Ralf

<Prev in Thread] Current Thread [Next in Thread>