From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Young Koh <young.koh@gmail.com>
Subject: Re: [uml-devel] a question about sigsetjmp() in copy_from/to_user()
Date: Wed, 28 Sep 2005 14:43:58 -0400 [thread overview]
Message-ID: <20050928184358.GA15224@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200509281926.44813.blaisorblade@yahoo.it>
On Wed, Sep 28, 2005 at 07:26:43PM +0200, Blaisorblade wrote:
> I'm not sure that would help anyway - if the host memory is full, it's full.
> It's just matter of waiting and retrying.
This isn't a matter of waiting and retrying. We use pages that are already
known to be good, and the rest go on a "bad pages" list and not freed, so
no one will try to use them again.
> I don't think the host would SIGBUS again on the same page specifically - or
> better, I'm almost sure this is not done.
> So, I don't see the reason for that. Catching SIGSEGV/SIGBUS is ok, taking
> another page is bad.
Catching SIGSEGV/SIGBUS at some random place in the kernel after it kmalloced
a bad page is OK? I don't think so.
The only way to keep the kernel running at that point is to get another
page and hope that it's OK. And if it's not, you try again.
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-09-28 19:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 14:06 [uml-devel] a question about sigsetjmp() in copy_from/to_user() Young Koh
2005-09-27 17:28 ` Jeff Dike
2005-09-28 11:59 ` Blaisorblade
2005-09-28 13:47 ` Young Koh
2005-09-28 14:50 ` Jeff Dike
2005-09-28 19:25 ` Young Koh
2005-09-29 12:09 ` Blaisorblade
2005-09-30 15:08 ` Young Koh
2005-09-30 15:44 ` Geert Uytterhoeven
2005-10-02 1:03 ` Jeff Dike
2005-10-02 10:23 ` Blaisorblade
2005-10-02 18:31 ` Jeff Dike
2005-10-03 18:35 ` Blaisorblade
2005-10-03 20:38 ` Jeff Dike
2005-09-28 16:09 ` Jeff Dike
2005-09-28 17:26 ` Blaisorblade
2005-09-28 18:43 ` Jeff Dike [this message]
2005-09-28 8:41 ` Blaisorblade
2005-09-28 14:22 ` Young Koh
2005-09-28 16:43 ` 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=20050928184358.GA15224@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=young.koh@gmail.com \
/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.