From: Dan Carpenter <error27@gmail.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-driver@qlogic.com,
"James E.J. Bottomley" <James.Bottomley@suse.de>,
Giridhar Malavali <giridhar.malavali@qlogic.com>,
Anirban Chakraborty <anirban.chakraborty@qlogic.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [patch] scsi/qla2xxx: checking for null cleanups
Date: Sat, 22 May 2010 20:30:36 +0000 [thread overview]
Message-ID: <20100522203036.GP22515@bicker> (raw)
These are two cleanups to make the static checkers happy. The "vha" is
used as the list cursor and can never be null so I removed the check. I
also modified qla2x00_request_firmware() to avoid a theoretical null
dereference. This is unlikely to happen I think, but it makes auditing
easier.
Signed-off-by: Dan Carpenter <error27@gmail.com>
diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c
index be1a8fc..d306853 100644
--- a/drivers/scsi/qla2xxx/qla_os.c
+++ b/drivers/scsi/qla2xxx/qla_os.c
@@ -2354,7 +2354,7 @@ qla2x00_remove_one(struct pci_dev *pdev)
ha = base_vha->hw;
list_for_each_entry_safe(vha, temp, &ha->vp_list, list) {
- if (vha && vha->fc_vport)
+ if (vha->fc_vport)
fc_vport_terminate(vha->fc_vport);
}
@@ -3689,6 +3689,8 @@ qla2x00_request_firmware(scsi_qla_host_t *vha)
blob = &qla_fw_blobs[FW_ISP81XX];
} else if (IS_QLA82XX(ha)) {
blob = &qla_fw_blobs[FW_ISP82XX];
+ } else {
+ return NULL;
}
mutex_lock(&qla_fw_lock);
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-driver@qlogic.com,
"James E.J. Bottomley" <James.Bottomley@suse.de>,
Giridhar Malavali <giridhar.malavali@qlogic.com>,
Anirban Chakraborty <anirban.chakraborty@qlogic.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [patch] scsi/qla2xxx: checking for null cleanups
Date: Sat, 22 May 2010 22:30:36 +0200 [thread overview]
Message-ID: <20100522203036.GP22515@bicker> (raw)
These are two cleanups to make the static checkers happy. The "vha" is
used as the list cursor and can never be null so I removed the check. I
also modified qla2x00_request_firmware() to avoid a theoretical null
dereference. This is unlikely to happen I think, but it makes auditing
easier.
Signed-off-by: Dan Carpenter <error27@gmail.com>
diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c
index be1a8fc..d306853 100644
--- a/drivers/scsi/qla2xxx/qla_os.c
+++ b/drivers/scsi/qla2xxx/qla_os.c
@@ -2354,7 +2354,7 @@ qla2x00_remove_one(struct pci_dev *pdev)
ha = base_vha->hw;
list_for_each_entry_safe(vha, temp, &ha->vp_list, list) {
- if (vha && vha->fc_vport)
+ if (vha->fc_vport)
fc_vport_terminate(vha->fc_vport);
}
@@ -3689,6 +3689,8 @@ qla2x00_request_firmware(scsi_qla_host_t *vha)
blob = &qla_fw_blobs[FW_ISP81XX];
} else if (IS_QLA82XX(ha)) {
blob = &qla_fw_blobs[FW_ISP82XX];
+ } else {
+ return NULL;
}
mutex_lock(&qla_fw_lock);
next reply other threads:[~2010-05-22 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 20:30 Dan Carpenter [this message]
2010-05-22 20:30 ` [patch] scsi/qla2xxx: checking for null cleanups 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=20100522203036.GP22515@bicker \
--to=error27@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=andrew.vasquez@qlogic.com \
--cc=anirban.chakraborty@qlogic.com \
--cc=giridhar.malavali@qlogic.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-driver@qlogic.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.