[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1103212057390.15815@swampdragon.chaosbits.net>
Date: Mon, 21 Mar 2011 21:04:26 +0100 (CET)
From: Jesper Juhl <jj@...osbits.net>
To: linux-scsi@...r.kernel.org
cc: linux-kernel@...r.kernel.org,
Adaptec OEM Raid Solutions <aacraid@...ptec.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
"James E.J. Bottomley" <James.Bottomley@...e.de>,
James Bottomley <jejb@...nel.org>
Subject: [PATCH][SCSI][resend] aacraid: Remove mem leak in
aac_send_raw_srb()
We leak in drivers/scsi/aacraid/commctrl.c::aac_send_raw_srb() :
We allocate memory:
...
struct user_sgmap* usg;
usg = kmalloc(actual_fibsize - sizeof(struct aac_srb)
+ sizeof(struct sgmap), GFP_KERNEL);
and then neglect to free it:
...
for (i = 0; i < usg->count; i++) {
u64 addr;
void* p;
if (usg->sg[i].count >
((dev->adapter_info.options &
AAC_OPT_NEW_COMM) ?
(dev->scsi_host_ptr->max_sectors << 9) :
65536)) {
rcode = -EINVAL;
goto cleanup;
... this 'goto' makes 'usg' go out of scope and leak the memory we
allocated.
Other exits properly kfree(usg), it's just here it is neglected.
Signed-off-by: Jesper Juhl <jj@...osbits.net>
---
commctrl.c | 1 +
1 file changed, 1 insertion(+)
patch against current Linus tree.
compile tested only, but I'm pretty certain it is sound.
diff --git a/drivers/scsi/aacraid/commctrl.c b/drivers/scsi/aacraid/commctrl.c
index 645ddd9..33370fb 100644
--- a/drivers/scsi/aacraid/commctrl.c
+++ b/drivers/scsi/aacraid/commctrl.c
@@ -649,6 +649,7 @@ static int aac_send_raw_srb(struct aac_dev* dev, void __user * arg)
AAC_OPT_NEW_COMM) ?
(dev->scsi_host_ptr->max_sectors << 9) :
65536)) {
+ kfree(usg);
rcode = -EINVAL;
goto cleanup;
}
--
Jesper Juhl <jj@...osbits.net> http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.
--
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/
Powered by blists - more mailing lists