From: Sasha Levin Subject: Re: [PATCH] mm: kill kmemcheck Date: Wed, 11 Mar 2015 09:39:33 -0400 Message-ID: <55004595.7020304@oracle.com> References: <1426074547-21888-1-git-send-email-sasha.levin@oracle.com> <20150311081909.552e2052@grimm.local.home> <55003666.3020100@oracle.com> <20150311084034.04ce6801@grimm.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: LKML , linux-mm@kvack.org, netdev@vger.kernel.org, linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-crypto@vger.kernel.org To: Steven Rostedt Return-path: In-Reply-To: <20150311084034.04ce6801@grimm.local.home> Sender: linux-arch-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On 03/11/2015 08:40 AM, Steven Rostedt wrote: > On Wed, 11 Mar 2015 08:34:46 -0400 > Sasha Levin wrote: > >> > Fair enough. We knew there are existing kmemcheck users, but KASan should be >> > superior both in performance and the scope of bugs it finds. It also shouldn't >> > impose new limitations beyond requiring gcc 4.9.2+. >> > > Ouch! OK, then I can't use it. I'm currently compiling with gcc 4.6.3. > > It will be a while before I upgrade my build farm to something newer. Are you actually compiling new kernels with 4.6.3, or are you using older kernels as well? There's no real hurry to kill kmemcheck right now, but we do want to stop supporting that in favour of KASan. Thanks, Sasha