From: Ken Cox <jkc@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [Patch 1/2] iavf: Fix panic in iavf_remove
Date: Wed, 8 Dec 2021 04:21:52 -0600 [thread overview]
Message-ID: <20211208102153.669338-2-jkc@redhat.com> (raw)
In-Reply-To: <20211208102153.669338-1-jkc@redhat.com>
It's possible for the client_task to get scheduled by the watchdog
after cancel_delayed_work_sync(&adapter->client_task); This can cause
a panic because free_netdev() is called with the client_task still queued
on the work queue.
The stack backtrace usually looks similar to:
[ 121.272963] Workqueue: 0x0 (iavf)
[ 121.272969] RIP: 0010:__list_del_entry_valid.cold.1+0x20/0x4c
...
[ 121.272980] Call Trace:
[ 121.272985] move_linked_works+0x49/0xa0
[ 121.272988] pwq_activate_delayed_work+0x43/0x100
[ 121.272991] pwq_dec_nr_in_flight+0x5d/0x90
[ 121.272993] worker_thread+0x30/0x370
[ 121.272995] ? process_one_work+0x420/0x420
[ 121.272998] kthread+0x15d/0x180
[ 121.273000] ? __kthread_parkme+0xa0/0xa0
[ 121.273003] ret_from_fork+0x1f/0x40
Signed-off-by: Ken Cox <jkc@redhat.com>
---
drivers/net/ethernet/intel/iavf/iavf_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c
index 6c2afbc8acbcd..63eec7edbf60a 100644
--- a/drivers/net/ethernet/intel/iavf/iavf_main.c
+++ b/drivers/net/ethernet/intel/iavf/iavf_main.c
@@ -3940,7 +3940,6 @@ static void iavf_remove(struct pci_dev *pdev)
set_bit(__IAVF_IN_REMOVE_TASK, &adapter->crit_section);
cancel_delayed_work_sync(&adapter->init_task);
cancel_work_sync(&adapter->reset_task);
- cancel_delayed_work_sync(&adapter->client_task);
if (adapter->netdev_registered) {
unregister_netdev(netdev);
adapter->netdev_registered = false;
@@ -3974,6 +3973,7 @@ static void iavf_remove(struct pci_dev *pdev)
iavf_free_q_vectors(adapter);
cancel_delayed_work_sync(&adapter->watchdog_task);
+ cancel_delayed_work_sync(&adapter->client_task);
cancel_work_sync(&adapter->adminq_task);
--
2.31.1
next prev parent reply other threads:[~2021-12-08 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 10:21 [Intel-wired-lan] [Patch 0/2] iavf: Fix panics due to active work queues being freed in iavf_remove() Ken Cox
2021-12-08 10:21 ` Ken Cox [this message]
2021-12-11 11:25 ` [Intel-wired-lan] [Patch 1/2] iavf: Fix panic in iavf_remove Jankowski, Konrad0
2021-12-13 17:29 ` Jankowski, Konrad0
2021-12-13 18:26 ` Nguyen, Anthony L
2021-12-14 13:18 ` Ken Cox
2021-12-08 10:21 ` [Intel-wired-lan] [Patch 2/2] iavf: Prevent reset from being scheduled while adapter is being removed Ken Cox
2021-12-11 11:25 ` Jankowski, Konrad0
2021-12-13 17:48 ` Jankowski, Konrad0
2021-12-13 18:27 ` Nguyen, Anthony L
2021-12-14 13:19 ` Ken Cox
2021-12-14 13:21 ` [Intel-wired-lan] [Patch 0/2] iavf: Fix panics due to active work queues being freed in iavf_remove() Ken Cox
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=20211208102153.669338-2-jkc@redhat.com \
--to=jkc@redhat.com \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.