From: Jakub Kicinski <kuba@kernel.org>
To: "Oleksij Rempel" <linux@rempel-privat.de>
Cc: "Hubert Wiśniewski" <hubert.wisniewski.25632@gmail.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] net: usb: asix: deadlock on interface setup
Date: Tue, 2 Sep 2025 16:35:11 -0700 [thread overview]
Message-ID: <20250902163511.181fa76a@kernel.org> (raw)
In-Reply-To: <DCGHG5UJT9G3.2K1GHFZ3H87T0@gmail.com>
On Sun, 31 Aug 2025 10:50:35 +0200 Hubert Wiśniewski wrote:
> Trying to bring an AX88772B-based USB-Ethernet adapter up results in a
> deadlock if the adapter was suspended at the time. Most network-related
> software hangs up indefinitely as a result. This can happen on systems
> which configure USB power control to 'auto' by default, e.g. laptops
> running `tlp`.
Oleksij, this seems to date back to commit e0bffe3e6894 ("net: asix:
ax88772: migrate to phylink"). Taking rtnl_lock in runtime resume
callbacks is known to result in unhappiness :(
Could you check if commit e110bc825897 ("net: usb:
lan78xx: Convert to PHYLINK for improved PHY and MAC management")
isn't similarly flawed?
next prev parent reply other threads:[~2025-09-02 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 8:50 [REGRESSION] net: usb: asix: deadlock on interface setup Hubert Wiśniewski
2025-09-02 23:35 ` Jakub Kicinski [this message]
2025-09-03 6:46 ` Oleksij Rempel
2025-09-10 8:29 ` Hubert Wiśniewski
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=20250902163511.181fa76a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hubert.wisniewski.25632@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).