From: Wenchao Hao <haowenchao@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<linux-ide@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Zhiqiang Liu <liuzhiqiang26@huawei.com>,
Wenchao Hao <haowenchao@huawei.com>
Subject: [PATCH v2] ata: libata-scsi: Make __ata_scsi_queuecmd() parameters check more clearly
Date: Wed, 5 Jan 2022 15:27:48 -0500 [thread overview]
Message-ID: <20220105202747.1963919-1-haowenchao@huawei.com> (raw)
This is just a clean code. Since each branch of "if" state would check
scmd->cmd_len, so move the check of scmd->cmd_len out of "if" state to
simplify input parameters check.
And remove redundant init of xlat_func at hand
The patch do not change origin function logic.
Signed-off-by: Wenchao Hao <haowenchao@huawei.com>
---
drivers/ata/libata-scsi.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
index 313e9475507b..ab8a2833dfec 100644
--- a/drivers/ata/libata-scsi.c
+++ b/drivers/ata/libata-scsi.c
@@ -4023,16 +4023,15 @@ int __ata_scsi_queuecmd(struct scsi_cmnd *scmd, struct ata_device *dev)
ata_xlat_func_t xlat_func;
int rc = 0;
+ if (unlikely(!scmd->cmd_len))
+ goto bad_cdb_len;
+
if (dev->class == ATA_DEV_ATA || dev->class == ATA_DEV_ZAC) {
- if (unlikely(!scmd->cmd_len || scmd->cmd_len > dev->cdb_len))
+ if (unlikely(scmd->cmd_len > dev->cdb_len))
goto bad_cdb_len;
xlat_func = ata_get_xlat_func(dev, scsi_op);
} else {
- if (unlikely(!scmd->cmd_len))
- goto bad_cdb_len;
-
- xlat_func = NULL;
if (likely((scsi_op != ATA_16) || !atapi_passthru16)) {
/* relay SCSI command to ATAPI device */
int len = COMMAND_SIZE(scsi_op);
--
2.32.0
next reply other threads:[~2022-01-05 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 20:27 Wenchao Hao [this message]
2022-01-05 7:39 ` Damien Le Moal
2022-01-05 8:48 ` Wenchao Hao
2022-01-05 9:07 ` Damien Le Moal
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=20220105202747.1963919-1-haowenchao@huawei.com \
--to=haowenchao@huawei.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.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®