From: Michal Kubiak <michal.kubiak@intel.com>
To: Jijie Shao <shaojijie@huawei.com>
Cc: <yisen.zhuang@huawei.com>, <salil.mehta@huawei.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <shenjian15@huawei.com>,
<wangjie125@huawei.com>, <liuyonglong@huawei.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net 2/3] net: hns3: fix kernel crash when devlink reload during pf initialization
Date: Fri, 15 Mar 2024 18:48:43 +0100 [thread overview]
Message-ID: <ZfSJ+08L+Tr3zeGU@localhost.localdomain> (raw)
In-Reply-To: <20240315100748.2913882-3-shaojijie@huawei.com>
On Fri, Mar 15, 2024 at 06:07:47PM +0800, Jijie Shao wrote:
> From: Yonglong Liu <liuyonglong@huawei.com>
>
> The devlink reload process will access the hardware resources,
> but the register operation is before the hardware initialize
> done, so, if process the devlink reload during initializetion,
typo: initializetion -> initialization
Moreover, I would suggest to fix the syntax of that description because
it seems to be not obvious.
e.g. the register operation is done before the hardware is initialized
(but I may not get your intention)
> may lead the kernel crash. This patch check whether the NIC is
-> may lead to kernel crash
> initialized to fix the problem.
Maybe just: "Fix this by adding the check if the NIC initialization check" ?
>
> Fixes: b741269b2759 ("net: hns3: add support for registering devlink for PF")
> Signed-off-by: Yonglong Liu <liuyonglong@huawei.com>
> Signed-off-by: Jijie Shao <shaojijie@huawei.com>
> ---
> drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_devlink.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_devlink.c b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_devlink.c
> index 9a939c0b217f..80db4f7b05f6 100644
> --- a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_devlink.c
> +++ b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_devlink.c
> @@ -40,8 +40,9 @@ static int hclge_devlink_reload_down(struct devlink *devlink, bool netns_change,
> struct pci_dev *pdev = hdev->pdev;
> int ret;
>
> - if (test_bit(HCLGE_STATE_RST_HANDLING, &hdev->state)) {
> - dev_err(&pdev->dev, "reset is handling\n");
> + if (test_bit(HCLGE_STATE_RST_HANDLING, &hdev->state) ||
> + !test_bit(HCLGE_STATE_NIC_REGISTERED, &hdev->state)) {
> + dev_err(&pdev->dev, "reset is handling or driver removed\n");
> return -EBUSY;
> }
>
> --
> 2.30.0
>
>
Thanks,
Michal
next prev parent reply other threads:[~2024-03-15 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 10:07 [PATCH net 0/3] There are some bugfix for the HNS3 ethernet driver Jijie Shao
2024-03-15 10:07 ` [PATCH net 1/3] net: hns3: fix index limit to support all queue stats Jijie Shao
2024-03-15 17:33 ` Michal Kubiak
2024-03-15 10:07 ` [PATCH net 2/3] net: hns3: fix kernel crash when devlink reload during pf initialization Jijie Shao
2024-03-15 17:48 ` Michal Kubiak [this message]
2024-03-15 10:07 ` [PATCH net 3/3] net: hns3: mark unexcuted loopback test result as UNEXECUTED Jijie Shao
2024-03-15 18:07 ` Michal Kubiak
2024-03-16 11:17 ` Jijie Shao
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=ZfSJ+08L+Tr3zeGU@localhost.localdomain \
--to=michal.kubiak@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.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