From: Jerome Glisse <j.glisse@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Jerome Glisse <jglisse@redhat.com>
Subject: Re: [PATCH] mm: honor FOLL_GET flag in follow_hugetlb_page v2
Date: Wed, 8 May 2013 10:33:07 -0400 [thread overview]
Message-ID: <CAH3drwZym3+o2cUhB37Zi6ALj65Z7j+N1w9WA-t1+0xi7XjWaw@mail.gmail.com> (raw)
In-Reply-To: <CAHGf_=rFd7xktoom2kg_1QgoCrqsVwdo2gzVR6UDzvm53ngjgw@mail.gmail.com>
On Tue, May 7, 2013 at 10:41 PM, KOSAKI Motohiro
<kosaki.motohiro@gmail.com> wrote:
> On Tue, May 7, 2013 at 8:51 PM, Jerome Glisse <j.glisse@gmail.com> wrote:
>> On Tue, May 7, 2013 at 8:47 PM, KOSAKI Motohiro
>> <kosaki.motohiro@gmail.com> wrote:
>>> On Tue, May 7, 2013 at 6:58 PM, <j.glisse@gmail.com> wrote:
>>>> From: Jerome Glisse <jglisse@redhat.com>
>>>>
>>>> Do not increase page count if FOLL_GET is not set. None of the
>>>> current user can trigger the issue because none of the current
>>>> user call __get_user_pages with both the pages array ptr non
>>>> NULL and the FOLL_GET flags non set in other word all caller
>>>> of __get_user_pages that don't set the FOLL_GET flags also call
>>>> with pages == NULL.
>>>
>>> Because, __get_user_pages() doesn't allow pages==NULL and FOLL_GET is on.
>>
>> Yes but this allow pages != NULL and FOLL_GET not set and as i said
>> there is no such user of that yet and this is exactly what i was
>> trying to use.
>
> Why? The following bug_on inhibit both case.
Yes i get lost on the double negation, but still my patch is correct
and i am not using gup but follow_hugetlb_page directly and i run into
the issue. My patch does not change the behavior for current user,
just fix assumption new user might have when not setting the FOLL_GET
flags.
>>> VM_BUG_ON(!!pages != !!(gup_flags & FOLL_GET));
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-05-08 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 22:58 j.glisse
2013-05-08 0:47 ` KOSAKI Motohiro
2013-05-08 0:51 ` Jerome Glisse
2013-05-08 2:41 ` KOSAKI Motohiro
2013-05-08 14:33 ` Jerome Glisse [this message]
2013-05-08 23:41 ` KOSAKI Motohiro
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=CAH3drwZym3+o2cUhB37Zi6ALj65Z7j+N1w9WA-t1+0xi7XjWaw@mail.gmail.com \
--to=j.glisse@gmail.com \
--cc=jglisse@redhat.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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