From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] [PATCH] UML - Add a .note.SuSE section
Date: Tue, 21 Aug 2007 19:05:53 +0200 [thread overview]
Message-ID: <200708211905.59128.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20070816210508.GA10559@c2.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On giovedì 16 agosto 2007, Jeff Dike wrote:
> On Thu, Aug 16, 2007 at 10:04:55PM +0200, Sam Ravnborg wrote:
> > On Thu, Aug 16, 2007 at 03:26:39PM -0400, Jeff Dike wrote:
> > > The crash is in this section:
> > >
> > > __uml_setup_start = .;
> > > .uml.setup.init : { *(.uml.setup.init) }
> > > __uml_setup_end = .;
> >
> > This looks like a classic bug.
> > You wanted this:
> > .uml.setup.init : {
> > __uml_setup_start = .;
> > *(.uml.setup.init)
> > __uml_setup_end = .;
> > }
>
> Ooh, this sounds promising, thanks.
It's not the first time we hit effects of such bugs, is it? The .note.ABI-tag
fix, time ago, may be about the same problem. Can you double-check all UML
linker scripts for more instances of this bug?
Bye
--
"Doh!" (cit.), I've made another another mistake!
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-21 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 16:24 Jeff Dike
2007-08-16 16:30 ` Arjan van de Ven
2007-08-16 16:54 ` [stable] " Greg KH
2007-08-16 19:26 ` Jeff Dike
2007-08-16 20:04 ` Sam Ravnborg
2007-08-16 21:05 ` Jeff Dike
2007-08-21 17:05 ` Blaisorblade [this message]
2007-08-22 16:37 ` [uml-devel] " Jeff Dike
2007-08-23 14:50 ` Blaisorblade
2007-08-16 16:39 ` [stable] " Chris Wright
2007-08-16 19:30 ` Andi Kleen
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=200708211905.59128.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®