From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: willemb@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
yuma@redhat.com, Aleksandr.Loktionov@intel.com,
edumazet@google.com, madhu.chittim@intel.com,
anthony.l.nguyen@intel.com, Simon Horman <horms@kernel.org>,
kuba@kernel.org, intel-wired-lan@lists.osuosl.org,
decot@google.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH iwl-net] idpf: fix adapter NULL pointer dereference on reboot
Date: Mon, 10 Mar 2025 21:52:30 -0700 [thread overview]
Message-ID: <9fa390cf-526e-4ac8-82e8-99f616b807b6@intel.com> (raw)
In-Reply-To: <Z8qK/Z/8lYtdR2UM@mev-dev.igk.intel.com>
On 3/6/2025 9:58 PM, Michal Swiatkowski wrote:
> On Thu, Mar 06, 2025 at 04:39:56PM -0800, Emil Tantilov wrote:
>> Driver calls idpf_remove() from idpf_shutdown(), which can end up
>> calling idpf_remove() again when disabling SRIOV.
>>
>
> The same is done in other drivers (ice, iavf). Why here it is a problem?
> I am asking because heaving one function to remove is pretty handy.
> Maybe the problem can be fixed by some changes in idpf_remove() instead?
It was indeed handy, until we ran into the crash. I did look into fixing
it in idpf_remove(), but I don't think I have a lot of options. I can
simply check and exit on adapter being NULL, but this types of checks
are usually frowned upon, so I looked into alternatives.
The main difference between idpf and ice is that idpf will load on both
VF and PF devices. From what I can tell, the VFs created by ice are
supported by iavf (0x1889 device id). With VFs created, on idpf, we end
up calling into idpf_remove() twice. First on shutdown and then again
when idpf_remove calls into sriov_disable(), because the VF devices have
the same driver, hence the same remove routine.
>
>> echo 1 > /sys/class/net/<netif>/device/sriov_numvfs
>> reboot
>>
>> BUG: kernel NULL pointer dereference, address: 0000000000000020
>> ...
>> RIP: 0010:idpf_remove+0x22/0x1f0 [idpf]
>> ...
>> ? idpf_remove+0x22/0x1f0 [idpf]
>> ? idpf_remove+0x1e4/0x1f0 [idpf]
>> pci_device_remove+0x3f/0xb0
>> device_release_driver_internal+0x19f/0x200
>> pci_stop_bus_device+0x6d/0x90
>> pci_stop_and_remove_bus_device+0x12/0x20
>> pci_iov_remove_virtfn+0xbe/0x120
>> sriov_disable+0x34/0xe0
>> idpf_sriov_configure+0x58/0x140 [idpf]
>> idpf_remove+0x1b9/0x1f0 [idpf]
>> idpf_shutdown+0x12/0x30 [idpf]
>> pci_device_shutdown+0x35/0x60
>> device_shutdown+0x156/0x200
>> ...
>>
>> Replace the direct idpf_remove() call in idpf_shutdown() with
>> idpf_vc_core_deinit() and idpf_deinit_dflt_mbx(), which perform
>> the bulk of the cleanup, such as stopping the init task, freeing IRQs,
>> destroying the vports and freeing the mailbox.
>>
>> Reported-by: Yuying Ma <yuma@redhat.com>
>> Fixes: e850efed5e15 ("idpf: add module register and probe functionality")
>> Reviewed-by: Madhu Chittim <madhu.chittim@intel.com>
>> Signed-off-by: Emil Tantilov <emil.s.tantilov@intel.com>
>> ---
>> drivers/net/ethernet/intel/idpf/idpf_main.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/intel/idpf/idpf_main.c b/drivers/net/ethernet/intel/idpf/idpf_main.c
>> index b6c515d14cbf..bec4a02c5373 100644
>> --- a/drivers/net/ethernet/intel/idpf/idpf_main.c
>> +++ b/drivers/net/ethernet/intel/idpf/idpf_main.c
>> @@ -87,7 +87,11 @@ static void idpf_remove(struct pci_dev *pdev)
>> */
>> static void idpf_shutdown(struct pci_dev *pdev)
>> {
>> - idpf_remove(pdev);
>> + struct idpf_adapter *adapter = pci_get_drvdata(pdev);
>> +
>> + cancel_delayed_work_sync(&adapter->vc_event_task);
>> + idpf_vc_core_deinit(adapter);
>> + idpf_deinit_dflt_mbx(adapter);
>>
>> if (system_state == SYSTEM_POWER_OFF)
>> pci_set_power_state(pdev, PCI_D3hot);
>> --
>> 2.17.2
next prev parent reply other threads:[~2025-03-11 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 0:39 [Intel-wired-lan] [PATCH iwl-net] idpf: fix adapter NULL pointer dereference on reboot Emil Tantilov
2025-03-07 5:58 ` Michal Swiatkowski
2025-03-11 4:52 ` Tantilov, Emil S [this message]
2025-03-10 6:22 ` Simon Horman
2025-03-11 4:42 ` Tantilov, Emil S
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=9fa390cf-526e-4ac8-82e8-99f616b807b6@intel.com \
--to=emil.s.tantilov@intel.com \
--cc=Aleksandr.Loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=madhu.chittim@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=yuma@redhat.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