From: himanshu Madhani <hmadhani2024@gmail.com>
To: Zilin Guan <zilin@seu.edu.cn>
Cc: njavali@marvell.com, GR-QLogic-Storage-Upstream@marvell.com,
"James.Bottomley@hansenpartnership.com"
<James.Bottomley@HansenPartnership.com>,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn
Subject: Re: [PATCH] scsi: qla2xxx: Fix improper freeing of purex item
Date: Tue, 18 Nov 2025 12:44:24 -0800 [thread overview]
Message-ID: <45878638-8A5A-46E0-9223-BDDAD0C89362@gmail.com> (raw)
In-Reply-To: <20251113151246.762510-1-zilin@seu.edu.cn>
> On Nov 13, 2025, at 7:12 AM, Zilin Guan <zilin@seu.edu.cn> wrote:
>
> In qla2xxx_process_purls_iocb(), an item is allocated via
> qla27xx_copy_multiple_pkt(), which internally calls
> qla24xx_alloc_purex_item().
>
> The qla24xx_alloc_purex_item() function may return a pre-allocated item
> from a per-adapter pool for small allocations, instead of dynamically
> allocating memory with kzalloc().
>
> An error handling path in qla2xxx_process_purls_iocb() incorrectly uses
> kfree() to release the item. If the item was from the pre-allocated pool,
> calling kfree() on it is a bug that can lead to memory corruption.
>
> Fix this by using the correct deallocation function,
> qla24xx_free_purex_item(), which properly handles both dynamically
> allocated and pre-allocated items.
>
> Fixes: 875386b988578 ("scsi: qla2xxx: Add Unsolicited LS Request and Response Support for NVMe")
> Signed-off-by: Zilin Guan <zilin@seu.edu.cn>
> ---
> drivers/scsi/qla2xxx/qla_nvme.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/qla2xxx/qla_nvme.c b/drivers/scsi/qla2xxx/qla_nvme.c
> index 316594aa40cc..42eb65a62f1f 100644
> --- a/drivers/scsi/qla2xxx/qla_nvme.c
> +++ b/drivers/scsi/qla2xxx/qla_nvme.c
> @@ -1292,7 +1292,7 @@ void qla2xxx_process_purls_iocb(void **pkt, struct rsp_que **rsp)
> a.reason = FCNVME_RJT_RC_LOGIC;
> a.explanation = FCNVME_RJT_EXP_NONE;
> xmt_reject = true;
> - kfree(item);
> + qla24xx_free_purex_item(item);
> goto out;
> }
>
> --
> 2.34.1
>
>
Looks Good.
Reviewed-by: Himanshu Madhani <hmadhani2024@gmail.com <mailto:hmadhani2024@gmail.com>>
next prev parent reply other threads:[~2025-11-18 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 15:12 Zilin Guan
2025-11-18 20:44 ` himanshu Madhani [this message]
2025-11-20 3:39 ` Martin K. Petersen
2025-11-29 3:30 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45878638-8A5A-46E0-9223-BDDAD0C89362@gmail.com \
--to=hmadhani2024@gmail.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=njavali@marvell.com \
--cc=zilin@seu.edu.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®