blk requests are obtained (some memory is allocated for them)
by means of functions blk_get_request and blk_make_request.
After usage (usually with help of blk_execute_rq) these requests
should be put (and freed) with help of blk_put_request.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Marina Makienko <[email protected]>
---
drivers/target/target_core_pscsi.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/target/target_core_pscsi.c b/drivers/target/target_core_pscsi.c
index 6e32ff6..c048ede 100644
--- a/drivers/target/target_core_pscsi.c
+++ b/drivers/target/target_core_pscsi.c
@@ -1161,6 +1161,7 @@ static int pscsi_execute_cmd(struct se_cmd *cmd)
blk_execute_rq_nowait(pdv->pdv_sd->request_queue, NULL, req,
(cmd->sam_task_attr == MSG_HEAD_TAG),
pscsi_req_done);
+ blk_put_request(req);
return 0;
--
1.7.7
blk requests are obtained (some memory is allocated for them)
by means of functions blk_get_request and blk_make_request.
After usage (usually with help of blk_execute_rq) these requests
should be put (and freed) with help of blk_put_request.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Marina Makienko <[email protected]>
---
There is no problems in drivers/target/target_core_pscsi.c
Please ignore the previous message.
--
1.7.7