linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Young Koh <young.koh@gmail.com>
Subject: Re: [uml-devel] a question about sigsetjmp() in copy_from/to_user()
Date: Wed, 28 Sep 2005 19:26:43 +0200	[thread overview]
Message-ID: <200509281926.44813.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050928160946.GB12888@ccure.user-mode-linux.org>

On Wednesday 28 September 2005 18:09, Jeff Dike wrote:
> On Wed, Sep 28, 2005 at 01:59:48PM +0200, Blaisorblade wrote:

> > That wasn't the original reason - this is fine too, but as I explained in
> > the other mail, cat /dev/kmem will cause a copy_to_user() with invalid
> > kernel ("from") address. I remember because I discussed this with you at
> > length.

> Oh yeah.  I was thinking there was a different (and better) reason, but I
> couldn't remember what it was.

> Also, my reason isn't that good anyway.  I had a different fix a while ago,
> but it got lost somewhere.  I added an arch hook to get_free_pages which
> touched each allocated page under the cover of a setjmp.  If a page
> couldn't be allocated on the host, then it is put on a "bad pages" list,
> and another page is allocated instead.
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.

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.
-- 
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-09-28 17:28 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 [this message]
2005-09-28 18:43         ` Jeff Dike
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=200509281926.44813.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox