From: James Smart <James.Smart@Emulex.Com>
To: Dan Carpenter <error27@gmail.com>
Cc: james.bottomley@suse.de, linux-scsi@vger.kernel.org
Subject: Re: [patch] potential null deref in lpfc_els.c
Date: Tue, 8 Dec 2009 13:01:23 -0500 [thread overview]
Message-ID: <1260295303.6096.21.camel@wookie> (raw)
In-Reply-To: <1260295121.6096.19.camel@wookie>
> This patch is against 2.6.32-rc8.
>
> The issue was found by a static checker. If cmd==ELS_CMD_PLOGI, it
> is possible for ndlp to be NULL. We do check ndlp further down the
> function so that would also indicate that we should check ndlp here.
>
> Compile tested.
>
Dan,
Thanks. We never hit this as it's code specific to using debugfs, which
we don't turn on except for very rare occasions. Anyway, it is an error,
so it's worth correcting.
I've updated your patch to change the default value - I wanted to D_ID
to be a non-valid value.
-- james s
Signed-off-by: James Smart <james.smart@emulex.com>
---
lpfc_els.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -upNr a/drivers/scsi/lpfc/lpfc_els.c b/drivers/scsi/lpfc/lpfc_els.c
--- a/drivers/scsi/lpfc/lpfc_els.c 2009-12-08 09:43:11.000000000 -0500
+++ b/drivers/scsi/lpfc/lpfc_els.c 2009-12-08 12:36:56.000000000 -0500
@@ -2562,7 +2562,8 @@ lpfc_els_retry(struct lpfc_hba *phba, st
lpfc_debugfs_disc_trc(vport, LPFC_DISC_TRC_ELS_CMD,
"Retry ELS: wd7:x%x wd4:x%x did:x%x",
- *(((uint32_t *) irsp) + 7), irsp->un.ulpWord[4], ndlp->nlp_DID);
+ *(((uint32_t *) irsp) + 7), irsp->un.ulpWord[4],
+ (ndlp ? ndlp->nlp_DID : 0xFFFFFFFF));
switch (irsp->ulpStatus) {
case IOSTAT_FCP_RSP_ERROR:
next parent reply other threads:[~2009-12-08 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1260295121.6096.19.camel@wookie>
2009-12-08 18:01 ` James Smart [this message]
2009-12-09 10:52 ` [patch] potential null deref in lpfc_els.c Dan Carpenter
2009-12-05 12:35 Dan Carpenter
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=1260295303.6096.21.camel@wookie \
--to=james.smart@emulex.com \
--cc=error27@gmail.com \
--cc=james.bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
/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