Netdev List
 help / color / mirror / Atom feed
From: tanhuazhong <tanhuazhong@huawei.com>
To: Joe Perches <joe@perches.com>, <davem@davemloft.net>,
	<sergei.shtylyov@cogentembedded.com>
Cc: <netdev@vger.kernel.org>, <linuxarm@huawei.com>,
	<salil.mehta@huawei.com>, <yisen.zhuang@huawei.com>,
	<lipeng321@huawei.com>, <linyunsheng@huawei.com>
Subject: Re: [Patch V4 net 01/11] net: hns3: add error handler for hns3_nic_init_vector_data()
Date: Tue, 30 Oct 2018 09:21:10 +0800	[thread overview]
Message-ID: <1ce6639d-fa73-52f0-1b02-a9b8e64e3608@huawei.com> (raw)
In-Reply-To: <a90e8a502366fef14d599dfbbaaeffa85cc77198.camel@perches.com>



On 2018/10/30 1:44, Joe Perches wrote:
> On Mon, 2018-10-29 at 21:54 +0800, Huazhong Tan wrote:
>> When hns3_nic_init_vector_data() fails to map ring to vector,
>> it should cancel the netif_napi_add() that has been successfully
>> done and then exits.
> []
>> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c b/drivers/net/ethernet/hisilicon/hns3/hns3_enet.c
> []
>> @@ -2821,7 +2821,7 @@ static int hns3_nic_init_vector_data(struct hns3_nic_priv *priv)
>>   	struct hnae3_handle *h = priv->ae_handle;
>>   	struct hns3_enet_tqp_vector *tqp_vector;
>>   	int ret = 0;
>> -	u16 i;
>> +	int i, j;
>>   
>>   	hns3_nic_set_cpumask(priv);
>>   
>> @@ -2868,13 +2868,19 @@ static int hns3_nic_init_vector_data(struct hns3_nic_priv *priv)
>>   		hns3_free_vector_ring_chain(tqp_vector, &vector_ring_chain);
>>   
>>   		if (ret)
>> -			return ret;
>> +			goto map_ring_fail;
>>   
>>   		netif_napi_add(priv->netdev, &tqp_vector->napi,
>>   			       hns3_nic_common_poll, NAPI_POLL_WEIGHT);
>>   	}
>>   
>>   	return 0;
>> +
>> +map_ring_fail:
>> +	for (j = i - 1; j >= 0; j--)
>> +		netif_napi_del(&priv->tqp_vector[j].napi);
> 
> style trivia:
> 
> Error clearing is most commonly done without another variable
> by decrementing i in the loop.
> 

Hi, Joe.
Is the below one more suitable?

+
+map_ring_fail:
+	while(i--)
+		netif_napi_del(&priv->tqp_vector[i].napi);
+
+	return ret;

Or do you have any other better suggestion?
Thanks.

> 
> 
> .
> 

  reply	other threads:[~2018-10-30 10:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 13:54 [Patch V4 net 00/11] Bugfix for the HNS3 driver Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 01/11] net: hns3: add error handler for hns3_nic_init_vector_data() Huazhong Tan
2018-10-29 17:44   ` Joe Perches
2018-10-30  1:21     ` tanhuazhong [this message]
2018-10-30  1:31       ` Joe Perches
2018-10-30  1:43         ` tanhuazhong
2018-10-30  9:11   ` Sergei Shtylyov
2018-10-30 10:19     ` tanhuazhong
2018-10-29 13:54 ` [Patch V4 net 02/11] net: hns3: add error handler for hns3_get_ring_config/hns3_queue_to_ring Huazhong Tan
2018-10-30  9:09   ` Sergei Shtylyov
2018-10-30 10:17     ` tanhuazhong
2018-10-29 13:54 ` [Patch V4 net 03/11] net: hns3: bugfix for reporting unknown vector0 interrupt repeatly problem Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 04/11] net: hns3: bugfix for the initialization of command queue's spin lock Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 05/11] net: hns3: remove unnecessary queue reset in the hns3_uninit_all_ring() Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 06/11] net: hns3: bugfix for is_valid_csq_clean_head() Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 07/11] net: hns3: bugfix for hclge_mdio_write and hclge_mdio_read Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 08/11] net: hns3: fix incorrect return value/type of some functions Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 09/11] net: hns3: bugfix for handling mailbox while the command queue reinitialized Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 10/11] net: hns3: bugfix for rtnl_lock's range in the hclge_reset() Huazhong Tan
2018-10-29 13:54 ` [Patch V4 net 11/11] net: hns3: bugfix for rtnl_lock's range in the hclgevf_reset() Huazhong Tan

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=1ce6639d-fa73-52f0-1b02-a9b8e64e3608@huawei.com \
    --to=tanhuazhong@huawei.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linuxarm@huawei.com \
    --cc=linyunsheng@huawei.com \
    --cc=lipeng321@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=yisen.zhuang@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