[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260202155813.3f8fbc27@kernel.org>
Date: Mon, 2 Feb 2026 15:58:13 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Petr Oros <poros@...hat.com>
Cc: netdev@...r.kernel.org, ivecera@...hat.com, mschmidt@...hat.com, 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>, Paolo
Abeni <pabeni@...hat.com>, Stanislav Fomichev <sdf@...ichev.me>,
intel-wired-lan@...ts.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] iavf: fix deadlock in reset handling
On Mon, 2 Feb 2026 09:48:20 +0100 Petr Oros wrote:
> + netdev_unlock(netdev);
> + ret = wait_event_interruptible_timeout(adapter->reset_waitqueue,
> + !iavf_is_reset_in_progress(adapter),
> + msecs_to_jiffies(5000));
> + netdev_lock(netdev);
Dropping locks taken by the core around the driver callback
is obviously unacceptable. SMH.
Powered by blists - more mailing lists