linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
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: Sun, 2 Oct 2005 12:31:04 +0200	[thread overview]
Message-ID: <200510021231.05260.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20051002010812.GB4778@localhost.localdomain>

On Sunday 02 October 2005 03:08, Jeff Dike wrote:
> 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.
Ah, ok.

> > 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.
At least, if we save them separately from the jmpbuf_t, we can use them for 
sysrq t, without reimplementing setjmp() and longjmp(). Not nice, wastes 24 
bytes, but would work.

I have the doubt that the location of those registers is part of the ABI, 
(pending: find an example where I can be statically linked to glibc and 
dynamically linked to a library dynamically linked to glibc, and must pass 
jmpbuf_t between the two implementations)
even if the C names aren't part of the API, so we could copy the structure.

Probably, however, it's just better to test on, say, a Slackware 8.1, and hope 
for the best and go doing a fix when things change.
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
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

  reply	other threads:[~2005-10-02 23:07 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
2005-10-02 10:31       ` Blaisorblade [this message]
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=200510021231.05260.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=allan.graves@oracle.com \
    --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