linux-kernel - [PATCH] staging/asus_oled: Add NULL test for kmalloc

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>] [day] [month] [year] [list]

Message-Id: <201001072003.51722.PeterHuewe@gmx.de>
Date:	Thu, 7 Jan 2010 20:03:51 +0100
From:	Peter Huewe <PeterHuewe@....de>
To:	"Greg Kroah-Hartman" <gregkh@...e.de>
Cc:	Andre Haupt <andre@...wigglers.org>,
	"Kevin A. Granade" <kevin.granade@...il.com>,
	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
	sjakub@...il.com
Subject: [PATCH] staging/asus_oled: Add NULL test for kmalloc

From: Peter Huewe <peterhuewe@....de>
Date: Thu, 7 Jan 2010 19:57:36 +0100

This patch adds a NULL test to check wether kmalloc was successful or
not.

Signed-off-by: Peter Huewe <peterhuewe@....de>
---
 Patch against Linux-next of Do 7. Jan 19:59:41 CET 2010

 drivers/staging/asus_oled/asus_oled.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/drivers/staging/asus_oled/asus_oled.c b/drivers/staging/asus_oled/asus_oled.c
index 0c1fb0d..c597fb2 100644
--- a/drivers/staging/asus_oled/asus_oled.c
+++ b/drivers/staging/asus_oled/asus_oled.c
@@ -430,6 +430,11 @@ static ssize_t odev_set_picture(struct asus_oled_dev *odev,
 
 		kfree(odev->buf);
 		odev->buf = kmalloc(odev->buf_size, GFP_KERNEL);
+		if (odev->buf == NULL) {
+			odev->buf_size = 0;
+			printk(ASUS_OLED_ERROR "Out of memory!\n");
+			return -ENOMEM;
+		}
 
 		memset(odev->buf, 0xff, odev->buf_size);
 
-- 
1.6.4.4

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