From: ebiederm@xmission.com (Eric W. Biederman)
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: akpm <akpm@osdl.org>,
fastboot@lists.osdl.org, drepper@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Re: [announce] kexec for linux 2.6.6
Date: 13 May 2004 23:21:11 -0600 [thread overview]
Message-ID: <m1wu3fy46w.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20040512143233.0ee0405a.rddunlap@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> writes:
> On 12 May 2004 10:57:27 -0600 Eric W. Biederman wrote:
>
> | Ulrich Drepper <drepper@redhat.com> writes:
> |
> | > Eric W. Biederman wrote:
> | >
> | > > As a first draft we should be able to use the standard ELF mechanisms
> | > > for this. It is not like PIC shared libraries were new. Or is
> | > > there some specific problem you are thinking of with respect to
> | > > randomization?
> | >
> | > The official kernel does not have vdso randomization. Ingo has a patch
> | > for the Red Hat kernel which is used in the FC2 kernel. The patch
> | > effectively only changes the location at which the vdso is mapped. It
> | > does not change the vdso content. So the __kernel_vsyscall symbol in
> | > the vdso's symbol table is not changed.
>
> [1:]
> | > AT_SYSINFO is the right way to go forward but it is not directly
> | > accessible to userlevel code. And it is no pointer which will make
> | > architectures with function descriptors unhappy.
> |
> | It sounds like the vdso just needs to be treated as a prelinked
> | vdso. You can find everything you need with AT_SYSINFO_EHDR.
> |
> | In the case of function descriptors they should be in a data segment
> | that can get copied to another page, and corrected. Leaving the code
> | segment at it's randomized location.
>
> Andrew tells me that he is OK with reserving a syscall number for
> kexec, which is easy & quick. I don't know when vdso will be available
> (for non-x86[2]) or when the AT_SYSINFO data will work for userlevel
> code[1. above].
>
> So is there any reason not to reserve the syscall number for kexec
> for now? (patch is below)
>
> --
> ~Randy
>
>
> [2] kexec is currently only available for x86, but there is interest
> in it for ia64 and ppc64 at least.
Also been work on x86-64 and ppc32. So if we are going to reserve
syscall numbers it would also be nice to have those reserved as well.
Eric
next prev parent reply other threads:[~2004-05-14 5:22 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
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 [this message]
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=m1wu3fy46w.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=drepper@redhat.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®