From: Chris Metcalf <cmetcalf@tilera.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH v2] hugetlb: fix race condition in hugetlb_fault()
Date: Sun, 1 Apr 2012 12:51:49 -0400 [thread overview]
Message-ID: <4F7887A5.3060700@tilera.com> (raw)
In-Reply-To: <CAJd=RBBWx7uZcw=_oA06RVunPAGeFcJ7LY=RwFCyB_BreJb_kg@mail.gmail.com>
On 4/1/2012 8:10 AM, Hillf Danton wrote:
> On Sat, Mar 31, 2012 at 4:07 AM, Chris Metcalf <cmetcalf@tilera.com> wrote:
>> The race is as follows. Suppose a multi-threaded task forks a new
>> process, thus bumping up the ref count on all the pages. While the fork
>> is occurring (and thus we have marked all the PTEs as read-only), another
>> thread in the original process tries to write to a huge page, taking an
>> access violation from the write-protect and calling hugetlb_cow(). Now,
>> suppose the fork() fails. It will undo the COW and decrement the ref
>> count on the pages, so the ref count on the huge page drops back to 1.
>> Meanwhile hugetlb_cow() also decrements the ref count by one on the
>> original page, since the original address space doesn't need it any more,
>> having copied a new page to replace the original page. This leaves the
>> ref count at zero, and when we call unlock_page(), we panic.
>>
>> The solution is to take an extra reference to the page while we are
>> holding the lock on it.
>>
> If the following chart matches the above description,
>
> [...]
>
> would you please spin with description refreshed?
Done, and thanks! I added your timeline chart to my description; I figure
no harm in having it both ways.
>> Cc: stable@kernel.org
> Let Andrew do the stable work, ok?
Fair point. I'm used to adding the Cc myself for things I push through the
arch/tile tree. This of course does make more sense to go through Andrew,
so I'll remove it.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Chris Metcalf <cmetcalf@tilera.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH v2] hugetlb: fix race condition in hugetlb_fault()
Date: Sun, 1 Apr 2012 12:51:49 -0400 [thread overview]
Message-ID: <4F7887A5.3060700@tilera.com> (raw)
In-Reply-To: <CAJd=RBBWx7uZcw=_oA06RVunPAGeFcJ7LY=RwFCyB_BreJb_kg@mail.gmail.com>
On 4/1/2012 8:10 AM, Hillf Danton wrote:
> On Sat, Mar 31, 2012 at 4:07 AM, Chris Metcalf <cmetcalf@tilera.com> wrote:
>> The race is as follows. Suppose a multi-threaded task forks a new
>> process, thus bumping up the ref count on all the pages. While the fork
>> is occurring (and thus we have marked all the PTEs as read-only), another
>> thread in the original process tries to write to a huge page, taking an
>> access violation from the write-protect and calling hugetlb_cow(). Now,
>> suppose the fork() fails. It will undo the COW and decrement the ref
>> count on the pages, so the ref count on the huge page drops back to 1.
>> Meanwhile hugetlb_cow() also decrements the ref count by one on the
>> original page, since the original address space doesn't need it any more,
>> having copied a new page to replace the original page. This leaves the
>> ref count at zero, and when we call unlock_page(), we panic.
>>
>> The solution is to take an extra reference to the page while we are
>> holding the lock on it.
>>
> If the following chart matches the above description,
>
> [...]
>
> would you please spin with description refreshed?
Done, and thanks! I added your timeline chart to my description; I figure
no harm in having it both ways.
>> Cc: stable@kernel.org
> Let Andrew do the stable work, ok?
Fair point. I'm used to adding the Cc myself for things I push through the
arch/tile tree. This of course does make more sense to go through Andrew,
so I'll remove it.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2012-04-01 16:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 20:07 [PATCH] hugetlb: fix race condition in hugetlb_fault() Chris Metcalf
2012-03-30 20:07 ` Chris Metcalf
2012-03-31 12:27 ` Hillf Danton
2012-03-31 12:27 ` Hillf Danton
2012-03-30 19:37 ` [PATCH v2] arch/tile: support multiple huge page sizes dynamically Chris Metcalf
2012-03-30 19:37 ` Chris Metcalf
2012-03-31 14:03 ` Hillf Danton
2012-03-31 14:03 ` Hillf Danton
2012-03-30 19:37 ` [PATCH v3] " Chris Metcalf
2012-03-30 19:37 ` Chris Metcalf
2012-04-01 12:33 ` Hillf Danton
2012-04-01 12:33 ` Hillf Danton
2012-04-01 16:46 ` Chris Metcalf
2012-04-01 16:46 ` Chris Metcalf
2012-04-02 2:21 ` Hillf Danton
2012-04-02 2:21 ` Hillf Danton
2012-03-30 20:07 ` [PATCH v2] hugetlb: fix race condition in hugetlb_fault() Chris Metcalf
2012-03-30 20:07 ` Chris Metcalf
2012-04-01 12:10 ` Hillf Danton
2012-04-01 12:10 ` Hillf Danton
2012-04-01 16:51 ` Chris Metcalf [this message]
2012-04-01 16:51 ` Chris Metcalf
2012-03-30 20:07 ` [PATCH v3] " Chris Metcalf
2012-03-30 20:07 ` Chris Metcalf
2012-04-06 22:23 ` [PATCH v2] " Andrew Morton
2012-04-06 22:23 ` Andrew Morton
2012-04-06 23:10 ` Hugh Dickins
2012-04-06 23:10 ` Hugh Dickins
2012-04-06 23:26 ` Andrew Morton
2012-04-06 23:26 ` Andrew Morton
2012-04-06 23:35 ` Hugh Dickins
2012-04-06 23:35 ` Hugh Dickins
2012-04-07 0:25 ` Chris Metcalf
2012-04-07 0:25 ` Chris Metcalf
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=4F7887A5.3060700@tilera.com \
--to=cmetcalf@tilera.com \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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.