netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jijie Shao <shaojijie@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, shenjian15@huawei.com,
	salil.mehta@huawei.com, liuyonglong@huawei.com,
	wangpeiyang1@huawei.com, chenhao418@huawei.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: hns3: fix kernel crash when uninstalling driver
Date: Mon, 4 Nov 2024 17:43:12 +0000	[thread overview]
Message-ID: <20241104174312.GG2118587@kernel.org> (raw)
In-Reply-To: <20241101091507.3644584-1-shaojijie@huawei.com>

On Fri, Nov 01, 2024 at 05:15:07PM +0800, Jijie Shao wrote:
> From: Peiyang Wang <wangpeiyang1@huawei.com>
> 
> When the driver is uninstalled and the VF is disabled concurrently, a
> kernel crash occurs. The reason is that the two actions call function
> pci_disable_sriov(). The num_VFs is checked to determine whether to
> release the corresponding resources. During the second calling, num_VFs
> is not 0 and the resource release function is called. However, the
> corresponding resource has been released during the first invoking.
> Therefore, the problem occurs:
> 
> [15277.839633][T50670] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020
> ...
> [15278.131557][T50670] Call trace:
> [15278.134686][T50670]  klist_put+0x28/0x12c
> [15278.138682][T50670]  klist_del+0x14/0x20
> [15278.142592][T50670]  device_del+0xbc/0x3c0
> [15278.146676][T50670]  pci_remove_bus_device+0x84/0x120
> [15278.151714][T50670]  pci_stop_and_remove_bus_device+0x6c/0x80
> [15278.157447][T50670]  pci_iov_remove_virtfn+0xb4/0x12c
> [15278.162485][T50670]  sriov_disable+0x50/0x11c
> [15278.166829][T50670]  pci_disable_sriov+0x24/0x30
> [15278.171433][T50670]  hnae3_unregister_ae_algo_prepare+0x60/0x90 [hnae3]
> [15278.178039][T50670]  hclge_exit+0x28/0xd0 [hclge]
> [15278.182730][T50670]  __se_sys_delete_module.isra.0+0x164/0x230
> [15278.188550][T50670]  __arm64_sys_delete_module+0x1c/0x30
> [15278.193848][T50670]  invoke_syscall+0x50/0x11c
> [15278.198278][T50670]  el0_svc_common.constprop.0+0x158/0x164
> [15278.203837][T50670]  do_el0_svc+0x34/0xcc
> [15278.207834][T50670]  el0_svc+0x20/0x30
> 
> For details, see the following figure.
> 
>      rmmod hclge              disable VFs
> ----------------------------------------------------
> hclge_exit()            sriov_numvfs_store()
>   ...                     device_lock()
>   pci_disable_sriov()     hns3_pci_sriov_configure()
>                             pci_disable_sriov()
>                               sriov_disable()
>     sriov_disable()             if !num_VFs :
>       if !num_VFs :               return;
>         return;                 sriov_del_vfs()
>       sriov_del_vfs()             ...
>         ...                       klist_put()
>         klist_put()               ...
>         ...                     num_VFs = 0;
>       num_VFs = 0;        device_unlock();
> 
> In this patch, when driver is removing, we get the device_lock()
> to protect num_VFs, just like sriov_numvfs_store().
> 
> Fixes: 0dd8a25f355b ("net: hns3: disable sriov before unload hclge layer")
> Signed-off-by: Peiyang Wang <wangpeiyang1@huawei.com>
> Signed-off-by: Jijie Shao <shaojijie@huawei.com>

Reviewed-by: Simon Horman <horms@kernel.org>

  reply	other threads:[~2024-11-04 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  9:15 [PATCH net] net: hns3: fix kernel crash when uninstalling driver Jijie Shao
2024-11-04 17:43 ` Simon Horman [this message]
2024-11-05 13:00 ` patchwork-bot+netdevbpf

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=20241104174312.GG2118587@kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=chenhao418@huawei.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=wangpeiyang1@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;
as well as URLs for NNTP newsgroup(s).