From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1427043AbcBSPn5 (ORCPT ); Fri, 19 Feb 2016 10:43:57 -0500 Received: from resqmta-ch2-09v.sys.comcast.net ([69.252.207.41]:36735 "EHLO resqmta-ch2-09v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422908AbcBSPn4 (ORCPT ); Fri, 19 Feb 2016 10:43:56 -0500 Date: Fri, 19 Feb 2016 09:43:54 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Dmitry Vyukov cc: Joonsoo Kim , Alexander Potapenko , Joonsoo Kim , Andrey Konovalov , Andrew Morton , Andrey Ryabinin , Steven Rostedt , kasan-dev , LKML , Linux Memory Management List Subject: Re: [PATCH v1 8/8] mm: kasan: Initial memory quarantine implementation In-Reply-To: Message-ID: References: <1cec06645310eeb495bcae7bed0807dbf2235f3a.1453918525.git.glider@google.com> <20160201024715.GC32125@js1304-P5Q-DELUXE> Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 19 Feb 2016, Dmitry Vyukov wrote: > No, this does not work. We've tried. > The problem is fragmentation. When all memory is occupied by slab, > it's already too late to reclaim memory. Free objects are randomly > scattered over memory, so if you have just 1% of live objects, the > chances are that you won't be able to reclaim any single page. Yes that is why slab objects *need* to be *movable*!!!