linux-kernel - Re: [openib-general] [PATCH 02/13] Device Discovery and ULLD Linkage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <455DF70C.7090400@pathscale.com>
Date:	Fri, 17 Nov 2006 09:53:16 -0800
From:	Bryan O'Sullivan <bos@...hscale.com>
To:	Steve Wise <swise@...ngridcomputing.com>
Cc:	rdreier@...co.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, openib-general@...nib.org
Subject: Re: [openib-general] [PATCH 02/13] Device Discovery and ULLD Linkage

Steve Wise wrote:

> +static inline void *vzmalloc(int size)
> +{
> +	void *p = vmalloc(size);
> +	memset(p, 0, size);
> +	return p;
> +}

This isn't checking the return value from vmalloc.

Also, we could do with a generic vzalloc and vcalloc, just as we now 
have kzalloc and kcalloc.  There are lots of routines like this sitting 
around.

	<b
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/