[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878th0vyas.fsf@xmission.com>
Date: Wed, 27 Sep 2017 12:36:27 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Levin\, Alexander \(Sasha Levin\)" <alexander.levin@...izon.com>
Cc: Michal Hocko <mhocko@...nel.org>,
"akpm\@linux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
"David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH] mm: kill kmemcheck again
"Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com> writes:
> On Wed, Sep 27, 2017 at 05:02:07PM +0200, Michal Hocko wrote:
>>This is just too large to review manually. How have you generated the
>>patch?
>
> Manualy. Note that most of it (~95%) is the result of 'rm arch/x86/mm/kmemcheck'.
>
> Otherwise, I just removed all uses of __GFP_NOWARN/SLAB_NOWARN, and calls to
> various annotations throughout the code.
Do you mean GFP_NOTRACK? GFP_NOWARN has a different meaning.
> I'm not sure about i386 breakage, will take a look, doesn't seem to be too obvious.
Eric
Powered by blists - more mailing lists