Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754679AbdDKNqb (ORCPT ); Tue, 11 Apr 2017 09:46:31 -0400 Received: from mx2.suse.de ([195.135.220.15]:47291 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753504AbdDKNq1 (ORCPT ); Tue, 11 Apr 2017 09:46:27 -0400 Date: Tue, 11 Apr 2017 15:46:18 +0200 From: Michal Hocko To: Kees Cook Cc: Christoph Lameter , Andrew Morton , Pekka Enberg , David Rientjes , Joonsoo Kim , Linux-MM , LKML Subject: Re: [PATCH] mm: Add additional consistency check Message-ID: <20170411134618.GN6729@dhcp22.suse.cz> References: <20170331164028.GA118828@beast> <20170404113022.GC15490@dhcp22.suse.cz> <20170404151600.GN15132@dhcp22.suse.cz> <20170404194220.GT15132@dhcp22.suse.cz> <20170404201334.GV15132@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2224 Lines: 47 On Mon 10-04-17 21:58:22, Kees Cook wrote: > On Tue, Apr 4, 2017 at 1:13 PM, Michal Hocko wrote: > > On Tue 04-04-17 14:58:06, Cristopher Lameter wrote: > >> On Tue, 4 Apr 2017, Michal Hocko wrote: > >> > >> > On Tue 04-04-17 14:13:06, Cristopher Lameter wrote: > >> > > On Tue, 4 Apr 2017, Michal Hocko wrote: > >> > > > >> > > > Yes, but we do not have to blow the kernel, right? Why cannot we simply > >> > > > leak that memory? > >> > > > >> > > Because it is a serious bug to attempt to free a non slab object using > >> > > slab operations. This is often the result of memory corruption, coding > >> > > errs etc. The system needs to stop right there. > >> > > >> > Why when an alternative is a memory leak? > >> > >> Because the slab allocators fail also in case you free an object multiple > >> times etc etc. Continuation is supported by enabling a special resiliency > >> feature via the kernel command line. The alternative is selectable but not > >> the default. > > > > I disagree! We should try to continue as long as we _know_ that the > > internal state of the allocator is still consistent and a further > > operation will not spread the corruption even more. This is clearly not > > the case for an invalid pointer to kfree. > > > > I can see why checking for an early allocator corruption is not always > > feasible and you can only detect after-the-fact but this is not the case > > here and putting your system down just because some buggy code is trying > > to free something it hasn't allocated is not really useful. I completely > > agree with Linus that we overuse BUG way too much and this is just > > another example of it. > > Instead of the proposed BUG here, what's the correct "safe" return value? I would assume that _you_ as the one who proposes the change would take some time to read and understand the code and know this answer. This is how we do changes to the kernel: have an objective, understand the code and generate the patch. I am really sad that this particular patch has shown that you didn't bother to consider the later part and blindly applied something that you haven't thought through properly. Please try harder next time. -- Michal Hocko SUSE Labs