From: Andrea Arcangeli <aarcange@redhat.com>
To: Izik Eidus <ieidus@redhat.com>
Cc: Greg KH <greg@kroah.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
Hugh Dickins <hugh@veritas.com>
Subject: Re: open(2) says O_DIRECT works on 512 byte boundries?
Date: Sat, 7 Feb 2009 16:33:20 +0100 [thread overview]
Message-ID: <20090207153320.GA13276@random.random> (raw)
In-Reply-To: <498D8D53.6030007@redhat.com>
On Sat, Feb 07, 2009 at 03:32:03PM +0200, Izik Eidus wrote:
> we are opening here a tiny race:
>
> cpu#1 do get_user_pages_fast and fetch the pte (it think the pte is
> writeable)
> cpu#2 do ptep_set_wrprotect()
> cpu#2 check the mapcount against pagecount (it think that everything is
> fine and continue)
> cpu#1 only now do get_page()
>
> Anyway this is minor issue that can be probably solved by just:
> rechecking if the pte isnt read_only in gup_fast after we do the get_page()
Not needed, if I check page_count vs mapcount after marking the pte
readonly and after sending smp-tlb-flush there is no race.
> Anyway sound like a great idea to fix this issue!
The only problem I'm thinking now is the IPI flood that would be
generated if I send IPIs for every pte wrprotected in fork, that
sounds overkill. So to use the IPI fix I could have gup-fast take the
slow path first time around if PG_gup isn't set, and then only second
time take the lockless fast path when PG_gup is already set (PG_gup
gets set by follow_page under PT lock/mmap_sem read mode at
least). And fork/ksm would only send IPIs for PG_gup pages. However
that would make gup-fast slow the first time it runs on an
anonymous/hugetlb page with pte marked writeable and I'm unsure if
that's ok.
Otherwise we've to return to the plan of the slightly more complicated
fix.
prev parent reply other threads:[~2009-02-07 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 21:33 open(2) says O_DIRECT works on 512 byte boundries? Greg KH
2009-01-29 0:41 ` Robert Hancock
[not found] ` <20090129011758.GA26534@kroah.com>
2009-01-29 2:59 ` Michael Kerrisk
2009-01-29 3:13 ` Greg KH
2009-01-29 15:40 ` Jeff Moyer
2009-01-30 6:16 ` Greg KH
2009-01-29 5:13 ` KAMEZAWA Hiroyuki
2009-01-29 7:10 ` KOSAKI Motohiro
2009-01-30 6:17 ` Greg KH
2009-02-02 22:08 ` Andrea Arcangeli
2009-02-03 1:29 ` KAMEZAWA Hiroyuki
2009-02-03 2:31 ` Andrea Arcangeli
2009-02-03 2:55 ` KAMEZAWA Hiroyuki
2009-02-03 3:42 ` KAMEZAWA Hiroyuki
2009-02-06 17:55 ` Andrea Arcangeli
2009-02-03 3:50 ` Greg KH
2009-02-03 15:01 ` Andrea Arcangeli
2009-02-03 4:13 ` KAMEZAWA Hiroyuki
2009-02-03 4:38 ` KAMEZAWA Hiroyuki
2009-02-03 15:08 ` Andrea Arcangeli
2009-02-04 23:41 ` Greg KH
2009-02-06 17:54 ` Andrea Arcangeli
2009-02-06 18:38 ` Andrea Arcangeli
2009-02-07 13:32 ` Izik Eidus
2009-02-07 15:33 ` Andrea Arcangeli [this message]
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=20090207153320.GA13276@random.random \
--to=aarcange@redhat.com \
--cc=greg@kroah.com \
--cc=hugh@veritas.com \
--cc=ieidus@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=npiggin@suse.de \
/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