Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756218Ab3J1LsG (ORCPT ); Mon, 28 Oct 2013 07:48:06 -0400 Received: from mail-pd0-f174.google.com ([209.85.192.174]:60335 "EHLO mail-pd0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756032Ab3J1LsE (ORCPT ); Mon, 28 Oct 2013 07:48:04 -0400 From: Rashika Kheria To: josh , opw-kernel@googlegroups.com, Minchan Kim , Jiang Liu , Nitin Gupta , Jerome Marchand , linux-kernel@vger.kernel.org, "linux-kernel @ vger . kernGreg KH" Subject: [PATCH v5 1/3] Staging: zram: Fix access of NULL pointer Date: Mon, 28 Oct 2013 17:17:51 +0530 Message-Id: X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <20131019110539.GA25167@gmail.com> References: <20131019110539.GA25167@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1369 Lines: 45 This patch fixes the bug in reset_store caused by accessing NULL pointer. Hence, It introduces a check for bdev. It also removes unnecessary check of bdev for fsync_bdev(). Signed-off-by: Rashika Kheria --- This revision fixes the following issues of the previous revision- Seperate patch into Bug Fix and Smatch Fix drivers/staging/zram/zram_drv.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/staging/zram/zram_drv.c b/drivers/staging/zram/zram_drv.c index 2c4ed52..d640a8f 100644 --- a/drivers/staging/zram/zram_drv.c +++ b/drivers/staging/zram/zram_drv.c @@ -648,6 +648,9 @@ static ssize_t reset_store(struct device *dev, zram = dev_to_zram(dev); bdev = bdget_disk(zram->disk, 0); + if (!bdev) + return -EBUSY; + /* Do not reset an active device! */ if (bdev->bd_holders) return -EBUSY; @@ -660,8 +663,7 @@ static ssize_t reset_store(struct device *dev, return -EINVAL; /* Make sure all pending I/O is finished */ - if (bdev) - fsync_bdev(bdev); + fsync_bdev(bdev); zram_reset_device(zram, true); return len; -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/