mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Sathya Prakash <sathya.prakash@broadcom.com>,
	Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
	Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
	Ranjan Kumar <ranjan.kumar@broadcom.com>,
	"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	"MPT-FusionLinux.pdl@broadcom.com"
	<MPT-FusionLinux.pdl@broadcom.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH] scsi: mpt3sas: fix invalid kfree of embedded event_data in event callback
Date: Thu, 30 Jul 2026 03:50:50 +0000	[thread overview]
Message-ID: <5a93a696e52a4ae9b660abc51b7aef65@baidu.com> (raw)
In-Reply-To: <20260706060840.2287-1-lirongqing@baidu.com>



> 
> From: Li RongQing <lirongqing@baidu.com>
> 
> fw_event->event_data is a flexible array member embedded within the
> fw_event_work structure (allocated as a single kzalloc). Calling
> kfree(fw_event->event_data) on it is invalid and can corrupt the heap, since it
> is not a separately allocated pointer.
> 
> The subsequent fw_event_work_put() will decrement the refcount to zero
> and call fw_event_work_free(), which frees the entire fw_event_work
> structure (including the embedded event_data). The extra kfree() is therefore
> both wrong and redundant.
> 
> Remove the erroneous kfree(fw_event->event_data) call in the
> MPI2_EVENT_SAS_TOPOLOGY_CHANGE_LIST error path. The PCIE topology
> change list handler already handles this correctly without the extra kfree.
> 
> Fixes: ad59571931072e6f ("scsi: mpt3sas: Add firmware event requeue
> support for busy devices")
> Signed-off-by: Li RongQing <lirongqing@baidu.com>

Ping

[Li,Rongqing] 


> ---
>  drivers/scsi/mpt3sas/mpt3sas_scsih.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> index 12caffe..ca01a49 100644
> --- a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> +++ b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
> @@ -12267,7 +12267,6 @@ mpt3sas_scsih_event_callback(struct
> MPT3SAS_ADAPTER *ioc, u8 msix_index,
>  		if (!fw_event->retries) {
> 
>  			ioc_err(ioc, "failure at %s:%d/%s()!\n",  __FILE__, __LINE__,
> __func__);
> -			kfree(fw_event->event_data);
>  			fw_event_work_put(fw_event);
>  			return 1;
>  		}
> --
> 2.9.4


      reply	other threads:[~2026-07-30  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  6:08 lirongqing
2026-07-30  3:50 ` Li,Rongqing [this message]

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=5a93a696e52a4ae9b660abc51b7aef65@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=MPT-FusionLinux.pdl@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ranjan.kumar@broadcom.com \
    --cc=sathya.prakash@broadcom.com \
    --cc=sreekanth.reddy@broadcom.com \
    --cc=suganath-prabu.subramani@broadcom.com \
    /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®