From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [PATCH]use kzalloc in vfs where appropriate Date: Fri, 17 Mar 2006 14:08:23 -0700 Message-ID: <20060317210823.GA8980@parisc-linux.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:38094 "EHLO palinux.hppa") by vger.kernel.org with ESMTP id S932781AbWCQVIY (ORCPT ); Fri, 17 Mar 2006 16:08:24 -0500 To: Oliver Neukum Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Mar 17, 2006 at 09:58:14PM +0100, Oliver Neukum wrote: > --- a/fs/bio.c 2006-03-11 23:12:55.000000000 +0100 > +++ b/fs/bio.c 2006-03-17 16:44:49.000000000 +0100 > @@ -635,12 +635,10 @@ > return ERR_PTR(-ENOMEM); > > ret = -ENOMEM; > - pages = kmalloc(nr_pages * sizeof(struct page *), GFP_KERNEL); > + pages = kzalloc(nr_pages * sizeof(struct page *), GFP_KERNEL); Didn't we just discuss this one and conclude it needed to use kcalloc instead?