From: Dan Carpenter <hidden> Date: 2012-05-17 07:11:33
In the original code if dma_pool_alloc() fails then we call
dma_pool_free(). The problem is that "chap_table" is NULL and
"chap_dma" is uninitialized so it will cause an error.
Signed-off-by: Dan Carpenter <redacted>
From: Dan Carpenter <hidden> Date: 2012-05-17 07:13:48
In the original code, if dma_pool_alloc() fails then we call
dma_pool_free(). It causes an error, possibly a NULL dereference.
Signed-off-by: Dan Carpenter <redacted>
@@ -2386,7 +2386,7 @@ sufficient_dsds:if(!ctx->fcp_cmnd){ql_log(ql_log_fatal,vha,0x3011,"Failed to allocate fcp_cmnd for cmd=%p.\n",cmd);-gotoqueuing_error_fcp_cmnd;+gotoqueuing_error;}/* Initialize the DSD list and dma handle */
From: Mike Christie <hidden> Date: 2012-05-17 15:55:55
On 05/17/2012 02:11 AM, Dan Carpenter wrote:
quoted hunk
In the original code if dma_pool_alloc() fails then we call
dma_pool_free(). The problem is that "chap_table" is NULL and
"chap_dma" is uninitialized so it will cause an error.
Signed-off-by: Dan Carpenter <redacted>
I thought dma_pool_free checked the vaddr/chap_table like how kfree
checks for nulls. You are right. Looks ok to me.
Reviewed-by: Mike Christie <redacted>
From: Chad Dupuis <hidden> Date: 2012-05-17 17:05:16
On Thu, 17 May 2012, Dan Carpenter wrote:
quoted hunk
In the original code, if dma_pool_alloc() fails then we call
dma_pool_free(). It causes an error, possibly a NULL dereference.
Signed-off-by: Dan Carpenter <redacted>
@@ -2386,7 +2386,7 @@ sufficient_dsds:if(!ctx->fcp_cmnd){ql_log(ql_log_fatal,vha,0x3011,"Failed to allocate fcp_cmnd for cmd=%p.\n",cmd);-gotoqueuing_error_fcp_cmnd;+gotoqueuing_error;}/* Initialize the DSD list and dma handle */--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks for the patch.
Acked-by: Chad Dupuis <redacted>
This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.