All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Question about PRIVATE_FUTEX
Date: Fri, 27 Mar 2009 05:56:26 +0100	[thread overview]
Message-ID: <49CC5C7A.9070505@cosmosbay.com> (raw)
In-Reply-To: <28c262360903261912n4ce235c6wf2f75b2be7faf0f4@mail.gmail.com>

Minchan Kim a écrit :
> Hi, Peter and Eric.
> 
> I am not expert about futex.
> I am sorry if this is dumb question.
> 
> If we use private futex, get_futex_key don't call get_user_pages_fast
> which pins page at page table.
> Then, get_futex_value_locked calls __cpy_from_user_inatomic with
> pagefault_disable.
> 
> Who make sure the user page is mapped at app's page table ?
> 

Nothing makes sure user page is mapped, as we dont have to (for private futexes
at least, since the 'key' is a combination of the futex virtual address (not
depending on the underlying physical page) and the task mm (sort of a static
offset per task)

If no page is mapped, a normal error should be returned to user, since
access to futex location will trigger a fault.



  parent reply	other threads:[~2009-03-27  5:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  2:12 Question about PRIVATE_FUTEX Minchan Kim
2009-03-27  4:32 ` Minchan Kim
2009-03-27  4:56 ` Eric Dumazet [this message]
2009-03-27  5:20   ` Minchan Kim
2009-03-27  5:50     ` Eric Dumazet
2009-03-27  6:20       ` Minchan Kim
2009-03-27  8:49 ` Peter Zijlstra
2009-03-27 10:56   ` Minchan Kim
2009-03-27 11:14     ` Peter Zijlstra
2009-03-27 11:37       ` Minchan Kim
2009-03-27 15:43         ` Darren Hart

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=49CC5C7A.9070505@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan.kim@gmail.com \
    --cc=peterz@infradead.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 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.