From: Weijie Gao <weijie.gao@mediatek.com>
To: <u-boot@lists.u-boot-project.org>
Cc: GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
Tom Rini <trini@konsulko.com>, Vignesh R <vigneshr@ti.com>,
Takahiro Kuwano <takahiro.kuwano@infineon.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Jeffrey Yu <jeyu@issi.com>,
Christoph Reiter <christoph.reiter@evk.biz>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Shiji Yang <yangshiji66@outlook.com>,
Bernhard Messerklinger <bernhard.messerklinger@at.abb.com>,
Vaishnav Achath <vaishnav.a@ti.com>,
Prasad Kummari <prasad.kummari@amd.com>
Subject: Re: [PATCH] net: lwip: handle chained pbufs in transmit path
Date: Mon, 27 Jul 2026 16:06:40 +0800 [thread overview]
Message-ID: <faff08bae1662e53c7752ed6a25b658d9c6c3efd.camel@mediatek.com> (raw)
In-Reply-To: <20260727080217.18208-1-weijie.gao@mediatek.com>
On Mon, 2026-07-27 at 16:02 +0800, Weijie Gao wrote:
> LwIP may pass a packet to the netif linkoutput callback as a chain
> of pbufs. In this case, p->len only describes the length of the
> first pbuf, while p->tot_len describes the length of the whole
> packet.
>
> The current transmit path only sends the first pbuf. This can
> truncate packets whose headers have already been generated for the
> full packet length, resulting in malformed frames on the wire.
> For example, the IP header may record a larger total length than the
> actual Ethernet frame length.
>
> Assemble chained pbufs into one aligned contiguous buffer before
> passing the packet to the Ethernet driver.
>
> Fixes: 98ad145db61a (net: lwip: add DHCP support and dhcp commmand)
> Signed-off-by: Weijie Gao <weijie.gao@mediatek.com>
> ---
> net/lwip/net-lwip.c | 45 ++++++++++++++++++++++++++++++++-----------
> --
> 1 file changed, 32 insertions(+), 13 deletions(-)
>
Sorry, I sent this patch by mistake. Please ignore it.
next prev parent reply other threads:[~2026-07-27 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 8:02 [PATCH] net: lwip: handle chained pbufs in transmit path Weijie Gao
2026-07-27 8:06 ` Weijie Gao [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-15 8:42 Weijie Gao
2026-07-16 7:56 ` Jerome Forissier
2026-07-16 8:00 ` Jerome Forissier
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=faff08bae1662e53c7752ed6a25b658d9c6c3efd.camel@mediatek.com \
--to=weijie.gao@mediatek.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=bernhard.messerklinger@at.abb.com \
--cc=christoph.reiter@evk.biz \
--cc=jeyu@issi.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=miquel.raynal@bootlin.com \
--cc=prasad.kummari@amd.com \
--cc=takahiro.kuwano@infineon.com \
--cc=trini@konsulko.com \
--cc=tudor.ambarus@linaro.org \
--cc=u-boot@lists.u-boot-project.org \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.com \
--cc=yangshiji66@outlook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox