From: Ken Cox <jkc@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [Patch 0/2] iavf: Fix panics due to active work queues being freed in iavf_remove()
Date: Tue, 14 Dec 2021 07:21:49 -0600 [thread overview]
Message-ID: <da53dc2c-d35f-94a8-68d2-affe5bed30d9@redhat.com> (raw)
In-Reply-To: <20211208102153.669338-1-jkc@redhat.com>
On 12/8/21 04:21, Ken Cox wrote:
> This series fixes panics that occur after iavf_remove() is called.
>
> The panics occur because the iavf_adapter structure is freed at the end
> of iavf_remove(), but it is possible that new work has been scheduled using
> the work_struct's contained within the iavf_adapter structure. If this occurs, the system will panic when it later tries to process the work queue.
>
> Ken Cox (2):
> iavf: Fix panic in iavf_remove
> iavf: Prevent reset from being scheduled while adapter is being
> removed
>
> drivers/net/ethernet/intel/iavf/iavf_ethtool.c | 7 +++++--
> drivers/net/ethernet/intel/iavf/iavf_main.c | 17 +++++++++++------
> drivers/net/ethernet/intel/iavf/iavf_virtchnl.c | 4 +++-
> 3 files changed, 19 insertions(+), 9 deletions(-)
>
NAK for this series.
These patches were generated off of the wrong branch. I will
re-evaluate and re-submit if necessary.
prev parent reply other threads:[~2021-12-14 13: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 ` [Intel-wired-lan] [Patch 1/2] iavf: Fix panic in iavf_remove Ken Cox
2021-12-11 11:25 ` 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 ` Ken Cox [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=da53dc2c-d35f-94a8-68d2-affe5bed30d9@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.