linux-um archives
 help / color / mirror / Atom feed
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: Sun, 2 Oct 2005 14:27:55 -0400	[thread overview]
Message-ID: <20051002182755.GB26063@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200510021231.05260.blaisorblade@yahoo.it>

On Sun, Oct 02, 2005 at 12:31:04PM +0200, Blaisorblade wrote:
> > 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.

Yup.

> I have the doubt that the location of those registers is part of the ABI, 

I think they are probably not.

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

Yeah, I agree.  On the positive side, I think that jmp_buf has probably been
unchanged for a long time, and will remain so.

				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

  reply	other threads:[~2005-10-02 18:35 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
2005-10-02 18:27         ` Jeff Dike [this message]
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=20051002182755.GB26063@ccure.user-mode-linux.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox