From: Dan Carpenter <dan.carpenter@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: Karen Xie <kxie@chelsio.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: cxgb3i: remove redundant null check and kfree on skb
Date: Tue, 14 Mar 2017 09:08:16 +0000 [thread overview]
Message-ID: <20170314090816.GH4136@mwanda> (raw)
In-Reply-To: <20170313191408.20080-1-colin.king@canonical.com>
On Mon, Mar 13, 2017 at 07:14:08PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> On the error exit path, skb is always null, so the non-null check
> and __kfree_skb call are redundant. Remove the redundant code,
> rename the rel_release label to err and make error paths jump to
> the err exit path.
>
> Detected by CoverityScan, CID#114328 ("Logically Dead Code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> index 1880eb6..f453a78 100644
> --- a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> +++ b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> @@ -972,21 +972,21 @@ static int init_act_open(struct cxgbi_sock *csk)
> &csk->daddr.sin_addr.s_addr);
> if (!csk->l2t) {
> pr_err("NO l2t available.\n");
> - return -EINVAL;
> + goto err;
err is a bad name because it doesn't say what the goto does. Imagine
if function names were so opaque. The most readable thing is a direct
return.
Also that's the least bug prone thing.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: Karen Xie <kxie@chelsio.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: cxgb3i: remove redundant null check and kfree on skb
Date: Tue, 14 Mar 2017 12:08:16 +0300 [thread overview]
Message-ID: <20170314090816.GH4136@mwanda> (raw)
In-Reply-To: <20170313191408.20080-1-colin.king@canonical.com>
On Mon, Mar 13, 2017 at 07:14:08PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> On the error exit path, skb is always null, so the non-null check
> and __kfree_skb call are redundant. Remove the redundant code,
> rename the rel_release label to err and make error paths jump to
> the err exit path.
>
> Detected by CoverityScan, CID#114328 ("Logically Dead Code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> index 1880eb6..f453a78 100644
> --- a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> +++ b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> @@ -972,21 +972,21 @@ static int init_act_open(struct cxgbi_sock *csk)
> &csk->daddr.sin_addr.s_addr);
> if (!csk->l2t) {
> pr_err("NO l2t available.\n");
> - return -EINVAL;
> + goto err;
err is a bad name because it doesn't say what the goto does. Imagine
if function names were so opaque. The most readable thing is a direct
return.
Also that's the least bug prone thing.
regards,
dan carpenter
next prev parent reply other threads:[~2017-03-14 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 19:14 [PATCH] scsi: cxgb3i: remove redundant null check and kfree on skb Colin King
2017-03-14 9:08 ` Dan Carpenter [this message]
2017-03-14 9:08 ` 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=20170314090816.GH4136@mwanda \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kxie@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.