From: Johannes Thumshirn <jthumshirn@suse.de>
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][V2] scsi: cxgb3i: remove redundant null check and kfree on skb
Date: Tue, 14 Mar 2017 11:34:31 +0000 [thread overview]
Message-ID: <20170314113431.GC4015@linux-x5ow.site> (raw)
In-Reply-To: <20170314104843.1358-1-colin.king@canonical.com>
On Tue, Mar 14, 2017 at 10:48:43AM +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 and
> just directly return with the appropriate error return code.
>
> Detected by CoverityScan, CID#114328 ("Logically Dead Code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> index 1880eb6..3c9f8cf2 100644
> --- a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> +++ b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> @@ -979,14 +979,14 @@ static int init_act_open(struct cxgbi_sock *csk)
> csk->atid = cxgb3_alloc_atid(t3dev, &t3_client, csk);
> if (csk->atid < 0) {
> pr_err("NO atid available.\n");
> - goto rel_resource;
> + return -EINVAL;
> }
> cxgbi_sock_set_flag(csk, CTPF_HAS_ATID);
> cxgbi_sock_get(csk);
>
> skb = alloc_wr(sizeof(struct cpl_act_open_req), 0, GFP_KERNEL);
> if (!skb)
> - goto rel_resource;
> + return -ENOMEM;
I don't think that's correct, not that it was before. cxgbi_sock_get(csk) does a
kref_get(&csk->refcnt), so this will at lease leak a kref. It will also "leak"
the atids_in_use in cxgb3_alloc_atid() as there's a call to cxgb3_free_atid()
missing. Looks like the complete cleanup path is worng here.
But I'd prefer having Karen or someone else at Chelsio confirm my assumptions.
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de>
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][V2] scsi: cxgb3i: remove redundant null check and kfree on skb
Date: Tue, 14 Mar 2017 12:34:31 +0100 [thread overview]
Message-ID: <20170314113431.GC4015@linux-x5ow.site> (raw)
In-Reply-To: <20170314104843.1358-1-colin.king@canonical.com>
On Tue, Mar 14, 2017 at 10:48:43AM +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 and
> just directly return with the appropriate error return code.
>
> Detected by CoverityScan, CID#114328 ("Logically Dead Code")
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> index 1880eb6..3c9f8cf2 100644
> --- a/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> +++ b/drivers/scsi/cxgbi/cxgb3i/cxgb3i.c
> @@ -979,14 +979,14 @@ static int init_act_open(struct cxgbi_sock *csk)
> csk->atid = cxgb3_alloc_atid(t3dev, &t3_client, csk);
> if (csk->atid < 0) {
> pr_err("NO atid available.\n");
> - goto rel_resource;
> + return -EINVAL;
> }
> cxgbi_sock_set_flag(csk, CTPF_HAS_ATID);
> cxgbi_sock_get(csk);
>
> skb = alloc_wr(sizeof(struct cpl_act_open_req), 0, GFP_KERNEL);
> if (!skb)
> - goto rel_resource;
> + return -ENOMEM;
I don't think that's correct, not that it was before. cxgbi_sock_get(csk) does a
kref_get(&csk->refcnt), so this will at lease leak a kref. It will also "leak"
the atids_in_use in cxgb3_alloc_atid() as there's a call to cxgb3_free_atid()
missing. Looks like the complete cleanup path is worng here.
But I'd prefer having Karen or someone else at Chelsio confirm my assumptions.
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-03-14 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 10:48 [PATCH][V2] scsi: cxgb3i: remove redundant null check and kfree on skb Colin King
2017-03-14 11:12 ` Dan Carpenter
2017-03-14 11:12 ` Dan Carpenter
2017-03-14 11:34 ` Johannes Thumshirn [this message]
2017-03-14 11:34 ` Johannes Thumshirn
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=20170314113431.GC4015@linux-x5ow.site \
--to=jthumshirn@suse.de \
--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.