[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ff86f0d-4f22-4afa-b84e-3dbc6e9910d7@intel.com>
Date: Fri, 6 Feb 2026 17:00:51 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Petr Oros <poros@...hat.com>, Anthony Nguyen <anthony.l.nguyen@...el.com>
CC: Tony Nguyen <anthony.l.nguyen@...el.com>, Przemek Kitszel
<przemyslaw.kitszel@...el.com>, Andrew Lunn <andrew+netdev@...n.ch>, "David
S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, "Jakub
Kicinski" <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, "Stanislav
Fomichev" <sdf@...ichev.me>, <intel-wired-lan@...ts.osuosl.org>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net] iavf: fix deadlock in reset handling
On 2/6/2026 2:04 AM, Petr Oros wrote:
> description...
>
> Fixes: 120f28a6f314 ("iavf: get rid of the crit lock")
> Signed-off-by: Petr Oros <poros@...hat.com>
> ---
Code changes look correct to me. Description obviously needs to get
written, but...
I loaded both the net as of ee9241524b46 ("amd-xgbe: do not select
NET_SELFTESTS when INET is disabled") and tested it with and without
this fix applied.
Before the fix, changing MTU till timeout after a few seconds with the
complaint, after which the reset will happen and MTU will be applied
late (the timeout in the wait event prevents a permanent deadlock). With
the fix the command completes quickly with no errors and the MTU change
applies immediately.
Tested-by: Jacob Keller <jacob.e.keller@...el.com>
Additionally, for a version with a proper commit message, please feel
free to add:
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Thanks for working on this, Petr!
Regards,
Jake
Powered by blists - more mailing lists