[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4D418F8D020000780002EC8F@vpn.id2.novell.com>
Date: Thu, 27 Jan 2011 14:30:21 +0000
From: "Jan Beulich" <JBeulich@...ell.com>
To: "Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Xiaowei Yang" <xiaowei.yang@...wei.com>
Cc: <fanhenglong@...wei.com>, "Kaushik Barde" <kbarde@...wei.com>,
"Kenneth Lee" <liguozhu@...wei.com>,
"linqaingmin" <linqiangmin@...wei.com>, <wangzhenguo@...wei.com>,
"Wu Fengguang" <fengguang.wu@...el.com>,
"Nick Piggin" <npiggin@...nel.dk>, <linux-kernel@...r.kernel.org>
Subject: Re: One (possible) x86 get_user_pages bug
>>> On 27.01.11 at 14:56, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> On Thu, 2011-01-27 at 21:05 +0800, Xiaowei Yang wrote:
>>
>> However, from the comments embedded in gup.c, it seems deliberate to
>> avoid the lock in the fast path. The question is: if so, how to avoid
>> the above scenario?
>
> Something like the below comes to mind... but I must say I haven't fully
> considered the problem yet..
That doesn't seem to account for the possible case of the page
even managing to get allocated again to something else.
And I think you would need to drop out of gup_pte_range() in
that case.
I would think this needs to be get_page_unless_zero()
followed by re-checking of the page table entry (probably
not even requiring a second gup_get_pte()); I'm not sure
yet what the correct action would be for change in only the
accessed/dirty bits.
Jan
> ---
> arch/x86/mm/gup.c | 9 +++++----
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/mm/gup.c b/arch/x86/mm/gup.c
> index dbe34b9..6527933 100644
> --- a/arch/x86/mm/gup.c
> +++ b/arch/x86/mm/gup.c
> @@ -89,10 +89,11 @@ static noinline int gup_pte_range(pmd_t pmd, unsigned
> long addr,
> }
> VM_BUG_ON(!pfn_valid(pte_pfn(pte)));
> page = pte_page(pte);
> - get_page(page);
> - SetPageReferenced(page);
> - pages[*nr] = page;
> - (*nr)++;
> + if (get_page_unless_zero(page)) {
> + SetPageReferenced(page);
> + pages[*nr] = page;
> + (*nr)++;
> + }
>
> } while (ptep++, addr += PAGE_SIZE, addr != end);
> pte_unmap(ptep - 1);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists