linux-um archives
 help / color / mirror / Atom feed
From: Young Koh <young.koh@gmail.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] a question about sigsetjmp() in copy_from/to_user()
Date: Wed, 28 Sep 2005 10:22:45 -0400	[thread overview]
Message-ID: <3524bf1f05092807222f9d0aed@mail.gmail.com> (raw)
In-Reply-To: <200509281041.15953.blaisorblade@yahoo.it>

so, as my understanding, sigsetjmp() is used for returning an error
when there is a userspace and/or kernelspace address faulting in both
skas and tt modes. and i386 implementation works the same way, i
guess.

my one quick question is (it could sound stupid, but) that why there
may be a kernelspace faulting? kernel must correct and shouldn't
access bad address, i guess, and if so, shouldn't it be a kernel
panic?

> In fact, what you see doesn't catch user space wrong addresses.
>
> It catches kernelspace faulting addresses - which is legal to happen, because
> i386 implementation catches any fault, and doesn't make a distinction, and
> which happens, when you try to do things like "cat /dev/kmem" - you're trying
> to do copy_to_user(to, offset /* which is 0 */, size).
>
> In fact, that sigsegjmp() was added back in 2.4.24-?um (IIRC) and then around
> ~2.6.7-um after I and Jeff analyzed this.

i'm using 2.4.26 and 2.6.12 and i think both versions include sigsetjmp().

Thank you,

-Young


-------------------------------------------------------
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 14:22 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
2005-09-28  8:41 ` Blaisorblade
2005-09-28 14:22   ` Young Koh [this message]
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=3524bf1f05092807222f9d0aed@mail.gmail.com \
    --to=young.koh@gmail.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