[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMGZ=FHDXRLZbq20zAFh+0w4zk4F4dUxsDd0amsyMo3Cb2ZrA@mail.gmail.com>
Date: Sat, 30 Sep 2017 15:57:27 +0200
From: Vegard Nossum <vegard.nossum@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Michal Hocko <mhocko@...nel.org>,
"Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
Alexander Potapenko <glider@...gle.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [PATCH] mm: kill kmemcheck again
On 30 September 2017 at 11:48, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 27 Sep 2017 17:02:07 +0200
> Michal Hocko <mhocko@...nel.org> wrote:
>
>> > Now that 2 years have passed, and all distros provide gcc that supports
>> > KASAN, kill kmemcheck again for the very same reasons.
>>
>> This is just too large to review manually. How have you generated the
>> patch?
>
> I agree. This needs to be taken out piece by piece, not in one go,
> where there could be unexpected fallout.
I have a patch from earlier this year that starts by removing the core
code and defining all the helpers/flags as no-ops so they can be
removed bit by bit at a later time. See the attachment. Pekka signed
off on it too.
I never actually submitted this because I was waiting for MSAN to be
merged in the kernel. It has been compile and run tested on x86_64.
Vegard
View attachment "0001-kmemcheck-remove-core-x86-mm-code.patch" of type "text/x-patch" (101897 bytes)
Powered by blists - more mailing lists