mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: Coywolf Qi Hunt <coywolf@gmail.com>,
	sam@ravnborg.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org
Subject: Re: i386-vmlinuxldss-distinguish-absolute-symbols.patch added to -mm tree
Date: Fri, 11 Nov 2005 23:40:05 -0700	[thread overview]
Message-ID: <m1wtjenzcq.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051111222627.24cf41f7.akpm@osdl.org> (Andrew Morton's message of "Fri, 11 Nov 2005 22:26:27 -0800")

Andrew Morton <akpm@osdl.org> writes:

> Coywolf Qi Hunt <coywolf@gmail.com> wrote:
>>
>> I wonder why this patch
>>  (i386-vmlinuxldss-distinguish-absolute-symbols.patch) isn't merged?
>
> Sam said scary things about it at the time but yes, it seems that things
> ended up OK.
>
> But Eric hasn't come back with the patch (>3 months) so perhaps its not
> very important, or is unneeded?

Mostly this is a piece of making the kernel relocatable, and I
have been holding off on that set of patches until I can get
the rest of the patches I have worked on for kexec on panic
merged.

I can only track so many bug reports at a time :)

This patch stands by itself so it should not be a problem.

One of the things I discovered when working with this patch is
that ld when can't actually cope with absolute symbols in a shared
library and will try and relocate them anyway.  I have code in my
tree that works around that particular ld bug but it is nowhere near
as nice as just specifying -shared when linking.  This patch is indeed
needed for that.

Eric

      reply	other threads:[~2005-11-12  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200507292019.j6TKJvXU019348@shell0.pdx.osdl.net>
2005-11-12  6:03 ` Coywolf Qi Hunt
2005-11-12  6:26   ` Andrew Morton
2005-11-12  6:40     ` Eric W. Biederman [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=m1wtjenzcq.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®