From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Allan Graves <allan.graves@oracle.com>
Subject: Re: [uml-devel] Clearing kmalloc_ok during shutdown is broken - malloc will clear our data.
Date: Sat, 1 Oct 2005 21:08:12 -0400 [thread overview]
Message-ID: <20051002010812.GB4778@localhost.localdomain> (raw)
In-Reply-To: <200509291614.03229.blaisorblade@yahoo.it>
On Thu, Sep 29, 2005 at 04:14:02PM +0200, Blaisorblade wrote:
> I now even found (by chance) the original mail from Allan Graves - and the
> changes in arch/um/include/sysdep-x86_64/ptrace.h weren't in his patch and
> are unrelated.
> Plus, I think they're also bogus (those registers exist), but I may be wrong,
The patch uses UPT_REG apparently for the first time. Those registers exist,
but there are no defines for them in the x86_64 ptrace.h. UPT_REG is never
called with any of those as its argument, so it's easy to just remove those
cases.
> On the bogus value: I'm more accustomed to 0xdeadbeef, since 0xbadbabe could
> be valid while 0xdeadbeef not (it's in the last giga).
Yeah, that makes sense.
> The only problem I see is that we need to test it on a wide glibc range -
> you're using an internal header detail, so glibc will break it at will.
Yeah, it's bad. The other way to do it is to explictly save the registers
in the thread struct, which is effectively the reimplementing setjmp option
which you mentioned.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-10-02 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 11:46 [uml-devel] Clearing kmalloc_ok during shutdown is broken - malloc will clear our data Blaisorblade
2005-09-28 20:12 ` Jeff Dike
2005-09-29 12:07 ` Blaisorblade
2005-09-28 21:31 ` Jeff Dike
2005-09-29 14:14 ` Blaisorblade
2005-10-02 1:08 ` Jeff Dike [this message]
2005-10-02 10:31 ` Blaisorblade
2005-10-02 18:27 ` Jeff Dike
2005-10-03 13:40 ` Allan Graves
2005-10-03 18:48 ` Blaisorblade
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=20051002010812.GB4778@localhost.localdomain \
--to=jdike@addtoit.com \
--cc=allan.graves@oracle.com \
--cc=blaisorblade@yahoo.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.