[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56C4B8DD.5040404@sr71.net>
Date: Wed, 17 Feb 2016 10:15:57 -0800
From: Dave Hansen <dave@...1.net>
To: Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, x86@...nel.org,
dave.hansen@...ux.intel.com, srikar@...ux.vnet.ibm.com,
vbabka@...e.cz, kirill.shutemov@...ux.intel.com,
aarcange@...hat.com, n-horiguchi@...jp.nec.com, jack@...e.cz
Subject: Re: [PATCH 02/33] mm: overload get_user_pages() functions
On 02/16/2016 12:36 AM, Ingo Molnar wrote:
>> > From: Dave Hansen <dave.hansen@...ux.intel.com>
>> >
>> > The concept here was a suggestion from Ingo. The implementation
>> > horrors are all mine.
>> >
>> > This allows get_user_pages(), get_user_pages_unlocked(), and
>> > get_user_pages_locked() to be called with or without the
>> > leading tsk/mm arguments. We will give a compile-time warning
>> > about the old style being __deprecated and we will also
>> > WARN_ON() if the non-remote version is used for a remote-style
>> > access.
> So at minimum this should be WARN_ON_ONCE(), to make it easier to recover some
> meaningful kernel log from such incidents.
I went to go fix this in the code but realized that I coded it up as
WARN_ONCE(). The description was just imprecise. So I won't be sending
a code fix for this.
Powered by blists - more mailing lists