public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "haowenchao (C)" <haowenchao2@huawei.com>
To: Sathya Prakash <sathya.prakash@broadcom.com>,
	Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
	Suganath Prabu Subramani  <suganath-prabu.subramani@broadcom.com>,
	"James E . J . Bottomley" <jejb@linux.ibm.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	<MPT-FusionLinux.pdl@broadcom.com>, <linux-scsi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <linfeilong@huawei.com>
Subject: Re: [PATCH] scsi: mpt3sas: fix NULL pointer access in mpt3sas_transport_port_add()
Date: Tue, 28 Feb 2023 22:49:08 +0800	[thread overview]
Message-ID: <5867eb0a-f42b-fac8-7ca7-e051a933fbaf@huawei.com> (raw)
In-Reply-To: <20230225100135.2109330-1-haowenchao2@huawei.com>

On 2023/2/25 18:01, Wenchao Hao wrote:
> port is allocated by sas_port_alloc_num() and rphy is allocated by
> sas_end_device_alloc() or sas_expander_alloc() which may return NULL,
> so we need to check the rphy to avoid possible NULL pointer access.
> 
> If sas_rphy_add() called with failure rphy is set to NULL, we would
> access the rphy in next lines which would also result NULL pointer
> access.
> 
> Fix commit 78316e9dfc24 ("scsi: mpt3sas: Fix possible resource leaks
> in mpt3sas_transport_port_add()")
> 
> Signed-off-by: Wenchao Hao <haowenchao2@huawei.com>
> ---
>   drivers/scsi/mpt3sas/mpt3sas_transport.c | 14 ++++++++++++--
>   1 file changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/scsi/mpt3sas/mpt3sas_transport.c b/drivers/scsi/mpt3sas/mpt3sas_transport.c
> index e5ecd6ada6cd..e8a4750f6ec4 100644
> --- a/drivers/scsi/mpt3sas/mpt3sas_transport.c
> +++ b/drivers/scsi/mpt3sas/mpt3sas_transport.c
> @@ -785,7 +785,7 @@ mpt3sas_transport_port_add(struct MPT3SAS_ADAPTER *ioc, u16 handle,
>   		goto out_fail;
>   	}
>   	port = sas_port_alloc_num(sas_node->parent_dev);
> -	if ((sas_port_add(port))) {
> +	if (!port || (sas_port_add(port))) {
>   		ioc_err(ioc, "failure at %s:%d/%s()!\n",
>   			__FILE__, __LINE__, __func__);
>   		goto out_fail;
> @@ -824,6 +824,12 @@ mpt3sas_transport_port_add(struct MPT3SAS_ADAPTER *ioc, u16 handle,
>   			    mpt3sas_port->remote_identify.sas_address;
>   	}
>   
> +	if (!rphy) {
> +		ioc_err(ioc, "failure at %s:%d/%s()!\n",
> +			__FILE__, __LINE__, __func__);
> +		goto out_delete_port;
> +	}
> +
>   	rphy->identify = mpt3sas_port->remote_identify;
>   
>   	if ((sas_rphy_add(rphy))) {
> @@ -831,6 +837,7 @@ mpt3sas_transport_port_add(struct MPT3SAS_ADAPTER *ioc, u16 handle,
>   			__FILE__, __LINE__, __func__);
>   		sas_rphy_free(rphy);
>   		rphy = NULL;
> +		goto out_delete_port;
>   	}
>   
>   	if (mpt3sas_port->remote_identify.device_type == SAS_END_DEVICE) {
> @@ -857,7 +864,10 @@ mpt3sas_transport_port_add(struct MPT3SAS_ADAPTER *ioc, u16 handle,
>   		    rphy_to_expander_device(rphy), hba_port->port_id);
>   	return mpt3sas_port;
>   
> - out_fail:
> +out_delete_port:
> +	sas_port_delete(port);
> +
> +out_fail:
>   	list_for_each_entry_safe(mpt3sas_phy, next, &mpt3sas_port->phy_list,
>   	    port_siblings)
>   		list_del(&mpt3sas_phy->port_siblings);

friendly ping...

  reply	other threads:[~2023-02-28 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 10:01 [PATCH] scsi: mpt3sas: fix NULL pointer access in mpt3sas_transport_port_add() Wenchao Hao
2023-02-28 14:49 ` haowenchao (C) [this message]
2023-03-07  1:42 ` Martin K. Petersen
2023-03-07 16:51   ` Sathya Prakash Veerichetty
2023-03-07 16:53 ` Sathya Prakash Veerichetty
2023-03-10  3:09 ` 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=5867eb0a-f42b-fac8-7ca7-e051a933fbaf@huawei.com \
    --to=haowenchao2@huawei.com \
    --cc=MPT-FusionLinux.pdl@broadcom.com \
    --cc=jejb@linux.ibm.com \
    --cc=linfeilong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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