All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [Patch 2/2] iavf: Prevent reset from being scheduled while adapter is being removed
Date: Mon, 13 Dec 2021 18:27:37 +0000	[thread overview]
Message-ID: <4ebe129aeecda496fcad40377903c14d9d0c2dec.camel@intel.com> (raw)
In-Reply-To: <20211208102153.669338-3-jkc@redhat.com>

On Wed, 2021-12-08 at 04:21 -0600, Ken Cox wrote:
> If a reset gets scheduled while the adapter is being removed it can
> cause a panic.
> 
> The work_struct for the reset_task is contained in the iavf_adapter
> structure.? iavf_remove() eventually frees the iavf_adapter structure
> so if there is active work scheduled it can cause a panic.
> 
> Signed-off-by: Ken Cox <jkc@redhat.com>

Like the other patch, this one isn't applying.

Thanks,
Tony

  parent reply	other threads:[~2021-12-13 18:27 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 [this message]
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=4ebe129aeecda496fcad40377903c14d9d0c2dec.camel@intel.com \
    --to=anthony.l.nguyen@intel.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.