From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
Allan Graves <allan.graves@oracle.com>
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Clearing kmalloc_ok during shutdown is broken - malloc will clear our data.
Date: Thu, 29 Sep 2005 16:14:02 +0200 [thread overview]
Message-ID: <200509291614.03229.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050928213125.GA16955@ccure.user-mode-linux.org>
On Wednesday 28 September 2005 23:31, Jeff Dike wrote:
> On Wed, Sep 28, 2005 at 01:46:15PM +0200, Blaisorblade wrote:
> > Also, there are some calls to kmalloc in the shutdown path - and they
> > work. I know this because I saw a problem with one of them: it gave
> > "might_sleep while atomic", and it was kmalloc in the shutdown, or
> > rather, in panic() - for the broken sysrq t (where's the fix you
> > promised?).
> Attached.
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,
I'm not looking at these unrelated changes since they pertain to something
else and I've no changelog.
On the patch: it makes sense, and the "XXX" removed comment, which explained
the bug, was added by myself.
On the bogus value: I'm more accustomed to 0xdeadbeef, since 0xbadbabe could
be valid while 0xdeadbeef not (it's in the last giga).
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.
Sadly, we haven't a better fix (except reimplementing setjmp(), which is even
worse than the original problem - plus I don't like glibc sources enough to
go picking the code).
--
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
next prev parent reply other threads:[~2005-09-29 19:22 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 [this message]
2005-10-02 1:08 ` Jeff Dike
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=200509291614.03229.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