From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ip/defrag: fix processing of last short fragment
Date: Sat, 19 Jun 2010 18:07:14 -0400 [thread overview]
Message-ID: <201006191807.15635.vapier@gentoo.org> (raw)
In-Reply-To: <0B45E93C5FF65740AEAE690BF3848B7A02087B75@rennsmail04.eu.thmulti.com>
On Friday, June 11, 2010 13:26:43 Fillod Stephane wrote:
> TFTP'ing a file of size 1747851 bytes with CONFIG_IP_DEFRAG and
> CONFIG_TFTP_BLOCKSIZE set to 4096 fails with a timeout, because
> the last fragment is not taken into account. This patch fixes
> IP fragments having less than 8 bytes of payload.
could we get this reviewed/merged before 2010.06 since it looks like kind of a
bad bug ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100619/46415a49/attachment.pgp
next prev parent reply other threads:[~2010-06-19 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 17:26 [U-Boot] [PATCH] ip/defrag: fix processing of last short fragment Fillod Stephane
2010-06-19 22:07 ` Mike Frysinger [this message]
2010-06-20 3:29 ` Ben Warren
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=201006191807.15635.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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