From: sashiko-bot@kernel.org
To: "Birger Koblitz" <mail@birger-koblitz.de>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next v17 03/13] ax88179_178a: Split driver into library and device specific code
Date: Wed, 07 Oct 2026 03:05:40 +0000 [thread overview]
Message-ID: <sashiko-outbox-162603@kernel.org> (raw)
In-Reply-To: <20261006-ax88179a-v17-3-252814fe35ea@birger-koblitz.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] net: deadlock in ax88179_change_mtu() due to recursive rtnl_lock()
--
commit bbebfb7ee3c4e848c7cc7bf989fd290de2e0c6f1
Author: Birger Koblitz <mail@birger-koblitz.de>
Subject: ax88179_178a: Split driver into library and device specific code
This commit splits the ax88179_178a module code into a common library and
device-specific code. It also renames the module to ax88179 and adds an
alias to the old name.
> diff --git a/drivers/net/usb/ax88179_lib.c b/drivers/net/usb/ax88179_lib.c
> new file mode 100644
> index 0000000000000..522ea2447a111
> --- /dev/null
> +++ b/drivers/net/usb/ax88179_lib.c
[ ... ]
> +int ax88179_change_mtu(struct net_device *net, int new_mtu)
> +{
> + struct usbnet *dev = netdev_priv(net);
> + u16 tmp16;
> +
> + WRITE_ONCE(net->mtu, new_mtu);
> + dev->hard_mtu = net->mtu + net->hard_header_len;
> +
> + rtnl_lock();
> + if (net->mtu > 1500) {
[Severity: High]
Does acquiring the RTNL lock here lead to a deadlock?
The core network stack already holds the RTNL mutex when it invokes the
.ndo_change_mtu callback (which is registered as ax88179_change_mtu in
ax88179_netdev_ops).
Since the RTNL mutex is non-recursive, attempting to acquire it again from
the same thread here in ax88179_change_mtu() will cause an immediate hang
whenever an MTU change is attempted on the network device.
> + ax88179_read_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
> + 2, 2, &tmp16);
> + tmp16 |= AX_MEDIUM_JUMBO_EN;
> + ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
> + 2, 2, &tmp16);
> + } else {
> + ax88179_read_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
> + 2, 2, &tmp16);
> + tmp16 &= ~AX_MEDIUM_JUMBO_EN;
> + ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
> + 2, 2, &tmp16);
> + }
> + rtnl_unlock();
> +
> + /* max qlen depend on hard_mtu and rx_urb_size */
> + usbnet_update_max_qlen(dev);
> +
> + return 0;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261006-ax88179a-v17-0-252814fe35ea@birger-koblitz.de?part=3
next prev parent reply other threads:[~2026-10-07 3:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 3:05 [PATCH net-next v17 00/13] ax88179_178a: Add support for AX88179A-based chips Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 01/13] phylink: Add phylink_mac_interrupt Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-07 3:55 ` Fwd: " Birger Koblitz
2026-10-07 12:18 ` Andrew Lunn
2026-10-07 14:16 ` Birger Koblitz
2026-10-08 3:34 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 02/13] phylib: Add support for PHYs with broken forced mode Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-08 3:36 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 03/13] ax88179_178a: Split driver into library and device specific code Birger Koblitz
2026-10-07 3:05 ` sashiko-bot [this message]
2026-10-08 3:38 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 04/13] ax88179_178a: Add HW support for AX179A-based chips Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-08 3:41 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 05/13] ax88179_178a: Add EEE configuration support for AX88179A MACs Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-06 3:05 ` [PATCH net-next v17 06/13] ax88179_178a: Add EEE configuration support for AX88179A PHYs Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-06 3:05 ` [PATCH net-next v17 07/13] ax88179_178a: Add VLAN offload support for AX88179A Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-08 3:44 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 08/13] ax88179_178a: Add AX179A/AX279 multicast configuration Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-06 3:05 ` [PATCH net-next v17 09/13] ax88179_178a: Add Suspend/resume support for AX88179A/772D/279 Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-08 3:47 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 10/13] ax88179_178a: Add ethtool get_drvinfo Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-06 3:05 ` [PATCH net-next v17 11/13] ax88179_178a: Update driver name and information Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-08 3:48 ` Birger Koblitz
2026-10-06 3:05 ` [PATCH net-next v17 12/13] ax88179_178a: Add support for AX88179A/772D/279 EEPROM access Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-06 3:05 ` [PATCH net-next v17 13/13] ax88796b: Add support for AX88772D, AX88179A and AX88279 Birger Koblitz
2026-10-07 3:05 ` sashiko-bot
2026-10-08 3:50 ` Birger Koblitz
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=sashiko-outbox-162603@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=sashiko-reviews@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