From: patchwork-bot+netdevbpf@kernel.org
To: Laurent Vivier <lvivier@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
sbrivio@redhat.com, kuba@kernel.org, oneukum@suse.com,
linux-usb@vger.kernel.org, jarod@redhat.com,
stable@vger.kernel.org
Subject: Re: [PATCH net v3] usbnet: cap max_mtu for drivers without bind callback
Date: Wed, 05 Aug 2026 01:20:15 +0000 [thread overview]
Message-ID: <178589281589.3863162.4194216540460778959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260731092711.857684-1-lvivier@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 31 Jul 2026 11:27:11 +0200 you wrote:
> usbnet_probe() initializes max_mtu to ETH_MAX_MTU and only caps it
> inside the if (info->bind) block. Drivers without a bind callback
> never enter this block, so max_mtu stays at ETH_MAX_MTU.
>
> QEMU's usb-net device (0x0525/0xa4a2) is claimed by the cdc_subset
> driver which has no bind callback. The guest accepts any MTU from DHCP
> (e.g. 65520 from passt), leading to TCP segments that exceed the
> device's 2048-byte receive buffer and are silently dropped.
>
> [...]
Here is the summary with links:
- [net,v3] usbnet: cap max_mtu for drivers without bind callback
https://git.kernel.org/netdev/net/c/1505b2cb6ae1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-05 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 9:27 [PATCH net v3] usbnet: cap max_mtu for drivers without bind callback Laurent Vivier
2026-08-05 1:20 ` patchwork-bot+netdevbpf [this message]
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=178589281589.3863162.4194216540460778959.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jarod@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=sbrivio@redhat.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.