public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: atomic copy_from_user?
Date: Mon, 22 Dec 2003 07:00:26 -0800	[thread overview]
Message-ID: <20031222150026.GD27687@holomorphy.com> (raw)
In-Reply-To: <1072054100.1742.156.camel@cube>

On Sun, Dec 21, 2003 at 07:48:20PM -0500, Albert Cahalan wrote:
> Surely I'm not the only one wanting such a beast...?
> From some naughty place in the code where might_sleep
> would trigger, I'd like to read from user memory.
> I'll pretty much assume that mlockall() has been
> called. Suppose that "current" is correct as well.
> I'd just use a pointer directly, except that:
> a. it isn't OK for the 4g/4g feature, s390, or sparc64
> b. it causes the "sparse" type checker to complain
> c. it will oops or worse if the user screwed up
> If the page is swapped out, I want a failed copy.

c.f. kmap_atomic() usage in mm/filemap.c


-- wli

  parent reply	other threads:[~2003-12-22 15:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22  0:48 atomic copy_from_user? Albert Cahalan
2003-12-22  4:31 ` Linus Torvalds
2003-12-22  9:36   ` Andrew Morton
2003-12-22 15:00 ` William Lee Irwin III [this message]
2003-12-22 18:26   ` Joe Korty
2003-12-22 20:55     ` Rob Love
2003-12-22 21:22       ` Joe Korty
2003-12-22 21:40         ` Rob Love
2003-12-22 21:59           ` Joe Korty
2003-12-22 22:14             ` Rob Love
2003-12-22 22:24             ` Andrew Morton
2003-12-22 22:06       ` Joe Korty
2003-12-22 22:18         ` Rob Love
2003-12-22 22:14       ` Andrew Morton
2003-12-22 22:19         ` Rob Love
2003-12-22 22:35           ` Joe Korty
2003-12-22 22:59             ` Rob Love

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=20031222150026.GD27687@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=albert@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    /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