mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "luobin (L)" <luobin9@huawei.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>, <luoxianjun@huawei.com>,
	<yin.yinshi@huawei.com>, <cloud.wangxiaoyun@huawei.com>
Subject: Re: [PATCH net v1] hinic: fix a bug of ndo_stop
Date: Sat, 9 May 2020 10:13:00 +0800	[thread overview]
Message-ID: <39a37452-c743-d1b5-d9dd-83d3058ee217@huawei.com> (raw)
In-Reply-To: <20200508142434.0c437e43@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

The two modified points are relevant. We bump the timeout for SET_FUNC_STATE

to ensure that cmd won't return failure when hw is busy. Otherwise hw 
may stomp

host memory if we free memory regardless of the return value of 
SET_FUNC_STATE.

I will mention the timeout changes in the commit message. And the bug 
exists since

the first commit, not introduced. Thanks for your review.

On 2020/5/9 5:24, Jakub Kicinski wrote:
> On Thu, 7 May 2020 18:22:27 +0000 Luo bin wrote:
>> if some function in ndo_stop interface returns failure because of
>> hardware fault, must go on excuting rest steps rather than return
>> failure directly, otherwise will cause memory leak
>>
>> Signed-off-by: Luo bin <luobin9@huawei.com>
> The code looks good, but would it make sense to split this patch into
> two? First one that ignores the return values on close path with these
> fixes tags:
>
> Fixes: e2585ea77538 ("net-next/hinic: Add Rx handler")
> Fixes: c4d06d2d208a ("net-next/hinic: Add Rx mode and link event handler")
>
> And a separate patch which bumps the timeout for SET_FUNC_STATE? Right
> now you don't even mention the timeout changes in the commit message.
> .

      reply	other threads:[~2020-05-09  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 18:22 Luo bin
2020-05-08 21:24 ` Jakub Kicinski
2020-05-09  2:13   ` luobin (L) [this message]

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=39a37452-c743-d1b5-d9dd-83d3058ee217@huawei.com \
    --to=luobin9@huawei.com \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luoxianjun@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=yin.yinshi@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®