linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] problems compiling 2.6.17 against glibc 2.4
Date: Sun, 25 Jun 2006 20:19:32 +0100	[thread overview]
Message-ID: <87mzc1hwl7.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <200606251638.31879.blaisorblade@yahoo.it> (blaisorblade@yahoo.it's message of "Sun, 25 Jun 2006 16:38:31 +0200")

On Sun, 25 Jun 2006, blaisorblade@yahoo.it announced authoritatively:
> On Wednesday 21 June 2006 21:38, Nix wrote:
[jmp_buf goes hidden]
>> This vile patch lets me compile but is almost certainly not good enough:
>> however, I don't know what *is* good enough: now that glibc is blocking
>> us from the layout of the jmp_buf, what's to stop them from changing it?
>> (Well, other than that it would break the ABI ;) )
> I made the same thought, but no, they have *already* changed it.
> Search for the message from Ulrich Drepper

It's not easy to find it given that little info :(

>                                            (and if you understand 
> the "security reasons" I'd be curious to hear them);

Well, there are obvious security problems with having pointers in
jmp_buf exposed: attackers who can exploit a buffer overflow and know
the location of a jmp_buf and its layout can force someone to longjmp()
to any location they like, regardless of -fstack-protector tricks. Even
FORTIFY_SOURCE won't protect against it if the buffer overrun didn't use
strcpy() or a similarly fortified call.

>                                                      also the below patch is 
> available in Jeff's tree from some time.

Aha, great minds kludge alike ;)

> I asked Jeff to #ifdef that code out for 2.6.17 release (since the below patch 
> was refused)... anyway Jeff found that we can take setjmp() implementation 
> from klibc and include it in UML.

Well, it wasn't ifdeffed out ;)

Using the uml setjmp() implementation seems like a good idea (or the uClibc one).

-- 
`NB: Anyone suggesting that we should say "Tibibytes" instead of
 Terabytes there will be hunted down and brutally slain.
 That is all.' --- Matthew Wilcox

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2006-06-25 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 19:38 [uml-devel] problems compiling 2.6.17 against glibc 2.4 Nix
2006-06-25 14:38 ` Blaisorblade
2006-06-25 19:19   ` Nix [this message]
2006-06-25 19:33     ` Blaisorblade
2006-06-26 16:26       ` Nix
2006-06-26 16:45         ` Blaisorblade
2006-06-26 17:09           ` Nix

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=87mzc1hwl7.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --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;
as well as URLs for NNTP newsgroup(s).