From: ebiederm@xmission.com (Eric W. Biederman)
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
Mikael Pettersson <mikpe@csd.uu.se>,
kai@tp1.ruhr-uni-bochum.de, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.59 vmlinux.lds.S change broke modules
Date: 17 Jan 2003 20:08:08 -0700 [thread overview]
Message-ID: <m1znpzdujr.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030117162104.GB1040@mars.ravnborg.org>
Sam Ravnborg <sam@ravnborg.org> writes:
> On Fri, Jan 17, 2003 at 09:13:14AM -0700, Eric W. Biederman wrote:
> > That has been roughly my experience on x86 as well with the exception
> > of bss sections. For bss sections placing the symbols inside the section
> > itself has been deadly.
>
> Could you elaborate a bit more what you have seen?
Sorry. Placing symbols inside .bss sections (sections by any name
that are not allocated) has occasionally given them values not as
expected. While at the same time placing the symbols around the .bss
sections has worked reliably for me.
Eric
next prev parent reply other threads:[~2003-01-18 2:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 12:55 2.5.59 vmlinux.lds.S change broke modules Mikael Pettersson
2003-01-17 13:44 ` Brian Gerst
2003-01-17 13:49 ` Mikael Pettersson
2003-01-17 14:32 ` Mike Galbraith
2003-01-17 13:56 ` Russell King
2003-01-17 16:13 ` Eric W. Biederman
2003-01-17 16:21 ` Sam Ravnborg
2003-01-18 3:08 ` Eric W. Biederman [this message]
2003-01-17 16:24 ` Kai Germaschewski
2003-01-17 16:50 ` Russell King
2003-01-17 16:19 ` Sam Ravnborg
2003-01-17 14:44 ` Kai Germaschewski
2003-01-18 0:11 ` Kai Germaschewski
2003-01-18 5:45 ` Christopher Faylor
2003-01-18 6:14 ` J Sloan
2003-01-18 8:00 ` Mike Galbraith
2003-01-18 9:23 ` Sam Ravnborg
2003-01-18 9:34 ` Mike Galbraith
[not found] ` <Pine.LNX.4.44.0301171808010.15056-100000@chaos.physics.uio wa.edu>
2003-01-18 9:07 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 13:27 Adam J. Richter
2003-01-18 14:36 Mikael Pettersson
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=m1znpzdujr.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=rmk@arm.linux.org.uk \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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