From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753518AbdDDTNL (ORCPT ); Tue, 4 Apr 2017 15:13:11 -0400 Received: from resqmta-ch2-04v.sys.comcast.net ([69.252.207.36]:52710 "EHLO resqmta-ch2-04v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752859AbdDDTNJ (ORCPT ); Tue, 4 Apr 2017 15:13:09 -0400 Date: Tue, 4 Apr 2017 14:13:06 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Michal Hocko cc: Kees Cook , Andrew Morton , Pekka Enberg , David Rientjes , Joonsoo Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: Add additional consistency check In-Reply-To: <20170404151600.GN15132@dhcp22.suse.cz> Message-ID: References: <20170331164028.GA118828@beast> <20170404113022.GC15490@dhcp22.suse.cz> <20170404151600.GN15132@dhcp22.suse.cz> Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfFNntIuK8KioJOSdrdlXDzPi3vxqhgBsfB8AGpA5NZ1m91MRLAeudowzyndXrcAN1NN1SHcJLvM0atcXWlZsGMD1n2uzLGxE9Xhy1b/GdX6WFRhp7Rg1 qWVK7ik0cnEmADq3SHhcCsu0a5sL4pqevbIiycmszPCQIb0lJ9FYSOhIZbYbds8f7/PsdlMC5ozjPlDiQXKQ7TQ6Jz9G87youJ85xVh5ToNjYESJJc8O85Wm gZQTaa4+WOA/QqJ2iXDc7bIKbQjaOeIJWVMyUqF5Z8GnfZDr4FbbgAJZ9xVoN7+6mX31P1IQGBBjBHvCsLcIVjlYEmZh2rFNMA6Y9u/J+Ao7C/NaK4gmXbg0 S56K1upZ/sqz+/bi6KjRM3d6Th+8eYw379O1nO27MO7HoCiFHp8= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f71.google.com (mail-it0-f71.google.com [209.85.214.71]) by kanga.kvack.org (Postfix) with ESMTP id CF5786B0038 for ; Tue, 4 Apr 2017 15:13:09 -0400 (EDT) Received: by mail-it0-f71.google.com with SMTP id y18so50341701itc.5 for ; Tue, 04 Apr 2017 12:13:09 -0700 (PDT) Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net. [2001:558:fe21:29:69:252:207:44]) by mx.google.com with ESMTPS id n185si9182263itb.50.2017.04.04.12.13.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Apr 2017 12:13:09 -0700 (PDT) Date: Tue, 4 Apr 2017 14:13:06 -0500 (CDT) From: Christoph Lameter Subject: Re: [PATCH] mm: Add additional consistency check In-Reply-To: <20170404151600.GN15132@dhcp22.suse.cz> Message-ID: References: <20170331164028.GA118828@beast> <20170404113022.GC15490@dhcp22.suse.cz> <20170404151600.GN15132@dhcp22.suse.cz> Content-Type: text/plain; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Kees Cook , Andrew Morton , Pekka Enberg , David Rientjes , Joonsoo Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org 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. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org