From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754590AbcBVTc4 (ORCPT ); Mon, 22 Feb 2016 14:32:56 -0500 Received: from aserp1040.oracle.com ([141.146.126.69]:45006 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752866AbcBVTcx (ORCPT ); Mon, 22 Feb 2016 14:32:53 -0500 Date: Mon, 22 Feb 2016 22:32:38 +0300 From: Dan Carpenter To: Greg Kroah-Hartman Cc: Sudip Mukherjee , Alison Schofield , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: [patch 4/6] staging: gdm72xx: zero out padding Message-ID: <20160222193238.GD23565@mwanda> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Source-IP: aserv0021.oracle.com [141.146.126.233] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We pad the start of this buffer with 256 bytes of padding. It's not clear to me exactly what's going on or how it's used but let's zero it out. Signed-off-by: Dan Carpenter diff --git a/drivers/staging/gdm72xx/usb_boot.c b/drivers/staging/gdm72xx/usb_boot.c index 3082987..4431a80 100644 --- a/drivers/staging/gdm72xx/usb_boot.c +++ b/drivers/staging/gdm72xx/usb_boot.c @@ -286,7 +286,7 @@ static int em_download_image(struct usb_device *usbdev, const char *img_name, return ret; } - buf = kmalloc(DOWNLOAD_CHUCK + pad_size, GFP_KERNEL); + buf = kzalloc(DOWNLOAD_CHUCK + pad_size, GFP_KERNEL); if (!buf) { release_firmware(firm); return -ENOMEM;