linux-kernel - Re: [PATCH] drivers: net: Remove remaining alloc/OOM messages

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: <511425BA.1040005@broadcom.com>
Date:	Thu, 7 Feb 2013 23:07:54 +0100
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Joe Perches" <joe@...ches.com>
cc:	netdev <netdev@...r.kernel.org>, linux-can@...r.kernel.org,
	linux-kernel@...r.kernel.org, e1000-devel@...ts.sourceforge.net,
	linux-usb@...r.kernel.org, linux-wireless@...r.kernel.org,
	ath9k-devel@...ts.ath9k.org, wil6210@....qualcomm.com,
	brcm80211-dev-list@...adcom.com,
	devicetree-discuss <devicetree-discuss@...ts.ozlabs.org>
Subject: Re: [PATCH] drivers: net: Remove remaining alloc/OOM messages

On 02/07/2013 10:46 PM, Joe Perches wrote:
> alloc failures already get standardized OOM
> messages and a dump_stack.
> 
> For the affected mallocs around these OOM messages:
> 
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Removed now unused stack variables.
> Removed unnecessary parentheses.
> Neatened alignment.

for brcm80211 driver files listed below:

Acked-by: Arend van Spriel <arend@...adcom.com>
> Signed-off-by: Joe Perches <joe@...ches.com>
> ---
> Let me know if you want multiple small patches instead.
> 
>  drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c |  5 +--
>  drivers/net/wireless/brcm80211/brcmfmac/usb.c      |  7 ++--


--
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/