From: Jakub Kicinski <kuba@kernel.org>
To: Petr Oros <poros@redhat.com>
Cc: netdev@vger.kernel.org, ivecera@redhat.com, mschmidt@redhat.com,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Stanislav Fomichev <sdf@fomichev.me>,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] iavf: fix deadlock in reset handling
Date: Mon, 2 Feb 2026 15:58:13 -0800 [thread overview]
Message-ID: <20260202155813.3f8fbc27@kernel.org> (raw)
In-Reply-To: <20260202084820.260033-1-poros@redhat.com>
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.
next prev parent reply other threads:[~2026-02-02 23:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 8:48 [PATCH net] iavf: fix deadlock in reset handling Petr Oros
2026-02-02 9:06 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-02-02 10:53 ` Jijie Shao
2026-02-02 13:30 ` Ivan Vecera
2026-02-02 23:58 ` Jakub Kicinski [this message]
2026-02-03 1:00 ` [Intel-wired-lan] " Jacob Keller
2026-02-03 8:44 ` Petr Oros
2026-02-03 10:19 ` Przemek Kitszel
2026-02-03 11:32 ` Petr Oros
2026-02-03 23:47 ` Jacob Keller
2026-02-04 6:12 ` Przemek Kitszel
2026-02-04 19:25 ` Jacob Keller
2026-02-05 12:24 ` Petr Oros
2026-02-05 23:37 ` Jacob Keller
2026-02-06 10:04 ` Petr Oros
2026-02-07 1:00 ` Jacob Keller
2026-02-07 3:01 ` Jakub Kicinski
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=20260202155813.3f8fbc27@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sdf@fomichev.me \
/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