From: Oliver Neukum <oliver@neukum.org>
To: mfbaustx <mfbaustx@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: copy_from_user / copy_to_user with no swap space
Date: Mon, 16 Oct 2006 21:28:44 +0200 [thread overview]
Message-ID: <200610162128.45229.oliver@neukum.org> (raw)
In-Reply-To: <op.thi3x1mvnwjy9v@titan>
Am Montag, 16. Oktober 2006 21:19 schrieb mfbaustx:
> So, IF you MUST copy_from/to_user when in the context of the process, AND
> IF you have no virtual memory/swapping, THEN must it not be true that you
> can ALWAYS dereferences your user space pointers?
No. Your code may be only partially paged into RAM.
The same can happen for any mmaped data.
Regards
Oliver
next prev parent reply other threads:[~2006-10-16 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 19:19 mfbaustx
2006-10-16 19:28 ` Oliver Neukum [this message]
2006-10-16 19:47 ` mfbaustx
2006-10-17 10:58 ` Horst H. von Brand
2006-10-17 12:00 ` Helge Hafting
2006-10-16 19:34 ` Al Viro
2006-10-16 19:39 ` Kyle Moffett
2006-10-16 20:26 ` mfbaustx
2006-10-16 20:21 ` Horst H. von Brand
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=200610162128.45229.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfbaustx@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
all inboxes | Powered by JetHome®