From: "Glaza, Jan" <jan.glaza@intel.com>
To: Faicker Mo <faicker.mo@zenlayer.com>
Cc: "intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>,
"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [bug report]iavf: deadlock on detach/attach vf to VM with net_failover
Date: Wed, 28 Aug 2024 13:48:37 +0200 [thread overview]
Message-ID: <5dfb65a7-8625-4149-9d8a-b6bcda530882@intel.com> (raw)
In-Reply-To: <SJ0PR20MB6079EE704620E28B3AD45286FA8B2@SJ0PR20MB6079.namprd20.prod.outlook.com>
On 8/26/2024 5:19 AM, Faicker Mo wrote:
> Hello, we met a problem with iavf driver, the ubuntu22.04 kernel 5.15.0-119 and 6.11rc4 both have the same problem.
>
>
>
> When the X710 VF is detached and attached to the VM with net_failover, the kworker thread in VM hang. The backtrace is
...
> It looks like a dead lock of adapter->crit_lock.
> A similar problem, https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220808175845.484968-1-ivecera@redhat.com/#2947762 <https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220808175845.484968-1-ivecera@redhat.com/#2947762>
>
Hello, we are attempting local reproduction and will work to analyze and
fix the issue. If you are able to, could you please provide us with the
reproduction commands or script to facilitate easier investigation and
rootcausing?
Best regards,
Jan
next prev parent reply other threads:[~2024-08-28 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 3:19 [Intel-wired-lan] [bug report]iavf: deadlock on detach/attach vf to VM with net_failover Faicker Mo
2024-08-28 11:48 ` Glaza, Jan [this message]
2024-08-29 3:27 ` [Intel-wired-lan] [EXTERNAL] " Faicker Mo
2024-09-13 14:50 ` Glaza, Jan
2024-09-18 3:43 ` [Intel-wired-lan] [EXTERNAL] " Faicker Mo
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=5dfb65a7-8625-4149-9d8a-b6bcda530882@intel.com \
--to=jan.glaza@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=faicker.mo@zenlayer.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox