linux-kernel - Re: [PATCH] mm: kill kmemcheck again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20171003170235.339e4620@gandalf.local.home>
Date:   Tue, 3 Oct 2017 17:02:35 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>,
        Vegard Nossum <vegard.nossum@...il.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 Mon, 2 Oct 2017 09:29:04 +0200
Michal Hocko <mhocko@...nel.org> wrote:

> Maybe splitting the patch into three: 1) remove all callers of kmemleak
> API and 2) remove arch/x86/mm/kmemcheck/ and 3) remove leftovers would
> be slightly easier to review. Maybe 2 and 3 would have some dependencies
> so they would have to end up in the same path.

Perhaps start with just marking kmemcheck broken to prevent new users
as well. Let that go in for a release, and then start removing it
afterward.

-- Steve