From: Ralf Baechle <ralf@oss.sgi.com>
To: Dan Aizenstros <daizenstros@quicklogic.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Oops in do_mounts.c file.
Date: Sun, 6 Jan 2002 23:15:28 -0200 [thread overview]
Message-ID: <20020106231528.A3806@dea.linux-mips.net> (raw)
In-Reply-To: <sc35a6be.092@quicklogic.com>; from daizenstros@quicklogic.com on Fri, Jan 04, 2002 at 12:57:00PM -0800
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 parent reply other threads:[~2002-01-07 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:57 Oops in do_mounts.c file Dan Aizenstros
2002-01-04 20:57 ` Dan Aizenstros
2002-01-07 1:15 ` Ralf Baechle [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=20020106231528.A3806@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=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 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.