From: Bart Van Assche <bvanassche@acm.org>
To: Huai-Yuan Liu <qq810974084@gmail.com>,
james.smart@broadcom.com, dick.kennedy@broadcom.com,
jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@outlook.com
Subject: Re: [PATCH] scsi: lpfc: Fix a possible null pointer dereference
Date: Wed, 3 Apr 2024 16:09:15 -0700 [thread overview]
Message-ID: <13a50e06-2b35-4cc6-a3ea-d6e070195db7@acm.org> (raw)
In-Reply-To: <20240403014006.969441-1-qq810974084@gmail.com>
On 4/2/24 6:40 PM, Huai-Yuan Liu wrote:
> In function lpfc_xcvr_data_show, the memory allocation with kmalloc might
> fail, thereby making rdp_context a null pointer. In the following context
> and functions that use this pointer, there are dereferencing operations,
> leading to null pointer dereference.
>
> To fix this issue, a null pointer check should be added. If it is null,
> write error message and jump to 'out_free_rdp'.
>
> Fixes: 479b0917e447 ("scsi: lpfc: Create a sysfs entry called lpfc_xcvr_data for transceiver info")
> Signed-off-by: Huai-Yuan Liu <qq810974084@gmail.com>
> ---
> drivers/scsi/lpfc/lpfc_attr.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/scsi/lpfc/lpfc_attr.c b/drivers/scsi/lpfc/lpfc_attr.c
> index b1c9107d3408..b11e5114b7f2 100644
> --- a/drivers/scsi/lpfc/lpfc_attr.c
> +++ b/drivers/scsi/lpfc/lpfc_attr.c
> @@ -1904,6 +1904,11 @@ lpfc_xcvr_data_show(struct device *dev, struct device_attribute *attr,
>
> /* Get transceiver information */
> rdp_context = kmalloc(sizeof(*rdp_context), GFP_KERNEL);
> + if (!rdp_context) {
> + len = scnprintf(buf, PAGE_SIZE - len,
> + "ERROR: Not enough memory\n");
> + goto out_free_rdp;
> + }
>
Has this patch been verified with checkpatch? Checkpatch should have
reported the following for the above patch:
Possible unnecessary 'out of memory' message
Thanks,
Bart.
next prev parent reply other threads:[~2024-04-03 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 1:40 Huai-Yuan Liu
2024-04-03 1:58 ` 刘怀远
2024-04-03 23:09 ` Bart Van Assche [this message]
2024-04-07 7:01 ` 刘怀远
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=13a50e06-2b35-4cc6-a3ea-d6e070195db7@acm.org \
--to=bvanassche@acm.org \
--cc=baijiaju1990@outlook.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qq810974084@gmail.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®