Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757210Ab2FZNkh (ORCPT ); Tue, 26 Jun 2012 09:40:37 -0400 Received: from mx2.parallels.com ([64.131.90.16]:52424 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756830Ab2FZNkg (ORCPT ); Tue, 26 Jun 2012 09:40:36 -0400 Message-ID: <4FE9BB25.60905@parallels.com> Date: Tue, 26 Jun 2012 17:37:41 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Frederic Weisbecker CC: Tejun Heo , Frederic Weisbecker , , , Andrew Morton , , David Rientjes , Pekka Enberg , Michal Hocko , Johannes Weiner , Christoph Lameter , , , Pekka Enberg , Suleiman Souhlal Subject: Re: [PATCH 11/11] protect architectures where THREAD_SIZE >= PAGE_SIZE against fork bombs References: <1340633728-12785-1-git-send-email-glommer@parallels.com> <1340633728-12785-12-git-send-email-glommer@parallels.com> <4FE89807.50708@redhat.com> <20120625183818.GH3869@google.com> <4FE9AF88.5070803@parallels.com> <20120626133838.GA11519@somewhere.redhat.com> In-Reply-To: <20120626133838.GA11519@somewhere.redhat.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2345 Lines: 55 On 06/26/2012 05:38 PM, Frederic Weisbecker wrote: > On Tue, Jun 26, 2012 at 04:48:08PM +0400, Glauber Costa wrote: >> On 06/25/2012 10:38 PM, Tejun Heo wrote: >>> On Mon, Jun 25, 2012 at 06:55:35PM +0200, Frederic Weisbecker wrote: >>>> On 06/25/2012 04:15 PM, Glauber Costa wrote: >>>> >>>>> Because those architectures will draw their stacks directly from >>>>> the page allocator, rather than the slab cache, we can directly >>>>> pass __GFP_KMEMCG flag, and issue the corresponding free_pages. >>>>> >>>>> This code path is taken when the architecture doesn't define >>>>> CONFIG_ARCH_THREAD_INFO_ALLOCATOR (only ia64 seems to), and has >>>>> THREAD_SIZE >= PAGE_SIZE. Luckily, most - if not all - of the >>>>> remaining architectures fall in this category. >>>>> >>>>> This will guarantee that every stack page is accounted to the memcg >>>>> the process currently lives on, and will have the allocations to fail >>>>> if they go over limit. >>>>> >>>>> For the time being, I am defining a new variant of THREADINFO_GFP, not >>>>> to mess with the other path. Once the slab is also tracked by memcg, >>>>> we can get rid of that flag. >>>>> >>>>> Tested to successfully protect against :(){ :|:& };: >>>>> >>>>> Signed-off-by: Glauber Costa >>>>> CC: Christoph Lameter >>>>> CC: Pekka Enberg >>>>> CC: Michal Hocko >>>>> CC: Kamezawa Hiroyuki >>>>> CC: Johannes Weiner >>>>> CC: Suleiman Souhlal >>>> >>>> >>>> Acked-by: Frederic Weisbecker >>> >>> Frederic, does this (with proper slab accounting added later) achieve >>> what you wanted with the task counter? >>> >> >> A note: Frederic may confirm, but I think he doesn't even need >> the slab accounting to follow to achieve that goal. > > Limiting is enough. But that requires internal accounting. > Yes, but why the *slab* needs to get involved? accounting task stack pages should be equivalent to what you were doing, even without slab accounting. Right ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/