mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	fastboot@lists.osdl.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Re: [announce] kexec for linux 2.6.6
Date: Wed, 12 May 2004 08:33:28 -0700	[thread overview]
Message-ID: <40A243C8.401@redhat.com> (raw)
In-Reply-To: <m13c66qicb.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:


>>  sym = dlsym (RTLD_DEFAULT, "the_symbol_name")
> [...]

> 
> For the momen the only finished port is x86, so we should be able
> to do that, it would make the kernel patch a little bigger though.
> Last time I saw that conversation I thought you didn't like symbols in
> the vdso for syscalls because it slowed things down.

I don't want to  use this in glibc for every syscall.  But for your
random application in need of a syscall it's fine.

And there is one more thing: the above code is actually not what should
be used.  The symbol able entries should be position independent.  So
one will have to compute the final address (which will be fun for archs
with function descriptors).  I'll have to see how randomization is
actually implemented.  The __kernel_vsyscall symbol is probably not
changed, so we need an out-of-band mechanisms to report the load address
to the userlevel code.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

  reply	other threads:[~2004-05-12 15:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  4:26 Randy.Dunlap
2004-05-12  5:00 ` Ulrich Drepper
2004-05-12  6:18   ` [Fastboot] " Eric W. Biederman
2004-05-12 15:33     ` Ulrich Drepper [this message]
2004-05-12 15:54       ` Eric W. Biederman
2004-05-12 16:31         ` Ulrich Drepper
2004-05-12 16:57           ` Eric W. Biederman
2004-05-12 21:32             ` Randy.Dunlap
2004-05-12 22:08               ` David Mosberger
2004-05-12 22:28                 ` Andrew Morton
2004-05-12 22:33                   ` David Mosberger
2004-05-12 23:16                     ` Andrew Morton
2004-05-12 23:27                       ` David Mosberger
2004-05-13  4:30                       ` Christoph Hellwig
2004-05-13  5:05                         ` Willy Tarreau
2004-05-13  5:21                           ` William Lee Irwin III
2004-05-13  5:48                           ` Christoph Hellwig
2004-05-13  6:06                         ` Eric W. Biederman
2004-05-13  6:20                           ` Andrew Morton
2004-05-13  6:39                             ` Eric W. Biederman
2004-05-13  7:33                           ` Christoph Hellwig
2004-05-13  7:37                             ` Andrew Morton
2004-05-13  7:49                               ` Christoph Hellwig
2004-05-13  8:04                                 ` Andrew Morton
2004-05-13 13:52                                   ` Eric W. Biederman
2004-05-13 15:02                                 ` Randy.Dunlap
2004-05-14  5:21               ` Eric W. Biederman
2004-05-14 18:14                 ` Adam Litke
2004-05-15  2:25                   ` Eric W. Biederman
2004-05-17  0:49                     ` H. Peter Anvin
2004-05-12  5:05 ` [Fastboot] " Eric W. Biederman

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=40A243C8.401@redhat.com \
    --to=drepper@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@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®