From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Zachary Amsden <zach@vmware.com>, Andrew Morton <akpm@osdl.org>,
virtualization@lists.osdl.org, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled
Date: Sun, 21 May 2006 12:41:19 +0200 [thread overview]
Message-ID: <20060521104119.GA21117@elte.hu> (raw)
In-Reply-To: <1148204118.31087.8.camel@localhost.localdomain>
* Rusty Russell <rusty@rustcorp.com.au> wrote:
> But it turns out that this is a known problem with FC1's glibc and the
> exec-shield patches (google for FC1 glibc vdso). [..]
no, i think that conclusion is wrong. The FC1 glibc and vdso problems
*when mixing a FC2 kernel with a FC1 glibc* were due to exec-shield
enforcing non-exec for the vdso.
> [...] When Ingo and Arjan convinced me to push their code from
> exec-shield, they conveniently didn't mention this.
this bug has nothing to do with nonexec restrictions. [ Also, this all
was _years_ and hundreds of bugs ago, when upstream's position was still
a cocky "who the hell needs protection against overflows" and "go away
with this non-exec crap" so we were pretty much alone trying to
introduce those features. So any suggestion of intention on our part
would be quite unfair. ]
Ingo
next prev parent reply other threads:[~2006-05-21 10:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 6:03 [PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch Rusty Russell
2006-05-16 6:47 ` Ingo Molnar
2006-05-16 8:16 ` Zachary Amsden
2006-05-16 8:40 ` Chris Wright
2006-05-16 8:59 ` Zachary Amsden
2006-05-17 7:49 ` Rusty Russell
2006-05-18 7:54 ` Ingo Molnar
2006-05-18 8:29 ` Gerd Hoffmann
2006-05-20 0:43 ` Andrew Morton
2006-05-20 1:03 ` Ingo Molnar
2006-05-20 1:11 ` Andrew Morton
2006-05-20 1:15 ` Linus Torvalds
2006-05-20 8:53 ` [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled Ingo Molnar
2006-05-20 9:26 ` Andrew Morton
2006-05-20 9:30 ` Zachary Amsden
2006-05-20 9:43 ` Zachary Amsden
2006-05-20 9:48 ` Andrew Morton
2006-05-20 10:04 ` Zachary Amsden
2006-05-21 4:38 ` Rusty Russell
2006-05-21 9:35 ` Rusty Russell
2006-05-21 9:52 ` Andrew Morton
2006-05-21 10:41 ` Ingo Molnar [this message]
2006-05-21 11:06 ` Rusty Russell
2006-05-20 9:54 ` Ingo Molnar
2006-05-20 10:16 ` [patch] add print_fatal_signals support Ingo Molnar
2006-05-21 11:03 ` [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled Ingo Molnar
2006-05-21 11:38 ` Ingo Molnar
2006-05-21 12:33 ` Andrew Morton
2006-05-21 14:10 ` Arjan van de Ven
2006-05-22 14:32 ` Alexey Kuznetsov
2006-05-20 1:16 ` [PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch Zachary Amsden
2006-05-20 1:49 ` Andi Kleen
2006-05-20 1:24 ` Arjan van de Ven
2006-05-22 16:29 ` Jakub Jelinek
2006-05-22 16:44 ` Zachary Amsden
2006-05-22 17:14 ` Andrew Morton
2006-05-22 17:27 ` Ingo Molnar
2006-05-22 17:46 ` Linus Torvalds
2006-05-22 19:09 ` Ingo Molnar
2006-05-22 19:40 ` Linus Torvalds
2006-05-22 19:14 ` Adrian Bunk
2006-05-22 19:45 ` Linus Torvalds
2006-05-22 17:53 ` Andrew Morton
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=20060521104119.GA21117@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
/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
Powered by JetHome