From: patchwork-bot+netdevbpf@kernel.org
To: Laurent Vivier <lvivier@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
oneukum@suse.com, kuba@kernel.org, netdev@vger.kernel.org,
sbrivio@redhat.com
Subject: Re: [PATCH net v2] usbnet: limit max_mtu based on device's hard_mtu
Date: Wed, 21 Jan 2026 03:10:07 +0000 [thread overview]
Message-ID: <176896500760.707355.7611917521322998807.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119075518.2774373-1-lvivier@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 19 Jan 2026 08:55:18 +0100 you wrote:
> The usbnet driver initializes net->max_mtu to ETH_MAX_MTU before calling
> the device's bind() callback. When the bind() callback sets
> dev->hard_mtu based the device's actual capability (from CDC Ethernet's
> wMaxSegmentSize descriptor), max_mtu is never updated to reflect this
> hardware limitation).
>
> This allows userspace (DHCP or IPv6 RA) to configure MTU larger than the
> device can handle, leading to silent packet drops when the backend sends
> packet exceeding the device's buffer size.
>
> [...]
Here is the summary with links:
- [net,v2] usbnet: limit max_mtu based on device's hard_mtu
https://git.kernel.org/netdev/net/c/c7159e960f14
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-21 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 7:55 [PATCH net v2] usbnet: limit max_mtu based on device's hard_mtu Laurent Vivier
2026-01-21 3:10 ` patchwork-bot+netdevbpf [this message]
2026-05-18 7:21 ` Matthias May
2026-05-18 7:36 ` Laurent Vivier
2026-05-18 11:26 ` Matthias May
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=176896500760.707355.7611917521322998807.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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 \
/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.