From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753811Ab0IFJFg (ORCPT ); Mon, 6 Sep 2010 05:05:36 -0400 Received: from smtp-out.google.com ([74.125.121.35]:12283 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753104Ab0IFJFe (ORCPT ); Mon, 6 Sep 2010 05:05:34 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:user-agent:mime-version:content-type:x-system-of-record; b=WF48kge+z55CL6Nd33NginouZOZwFFQR9Grq9Nja9XqEFtOs6HP5G/eZ4for9YRKc J+u+L2l2y9A4voJKfp9Zg== Date: Mon, 6 Sep 2010 02:05:27 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Andrew Morton cc: Neil Brown , Alasdair G Kergon , Chris Mason , Steven Whitehouse , Jens Axboe , Jan Kara , Frederic Weisbecker , linux-raid@vger.kernel.org, linux-btrfs@vger.kernel.org, cluster-devel@redhat.com, linux-ext4@vger.kernel.org, reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [patch v2 1/5] mm: add nofail variants of kmalloc kcalloc and kzalloc In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 1 Sep 2010, David Rientjes wrote: > Add kmalloc_nofail(), kcalloc_nofail(), and kzalloc_nofail(). These > functions are equivalent to kmalloc(), kcalloc(), and kzalloc(), > respectively, except that they will never return NULL and instead loop > forever trying to allocate memory. > > If the first allocation attempt fails because the page allocator doesn't > implicitly loop, a warning will be emitted, including a call trace. > Subsequent failures will suppress this warning. > > These were added as helper functions for documentation and auditability. > No future callers should be added. > Are there any objections to merging this series through -mm with the exception of the fifth patch for ntfs? That particular patch needs to have its WARN_ON_ONCE() condition rewritten since it fallbacks to vmalloc for high order allocs. Thanks.