* [U-Boot] [PATCH] net: tftp: Make sure timeout will not effect wrap offset
@ 2013-08-03 10:09 rockly
0 siblings, 0 replies; only message in thread
From: rockly @ 2013-08-03 10:09 UTC (permalink / raw)
To: u-boot
Hi:
When the block 0 store to the memory of client and timeout at this
moment. Because of no ACK packet, the server will send block 0 again,
if this client reconnect to the server at this time ,
TftpBlockWrapOffset will become larger than it should be.
Signed-off-by : Rockly <rocklygnome@gmail.com>
---
diff --git a/net/tftp.c b/net/tftp.c
index 6d333d5..2e06808 100644
--- a/net/tftp.c
+++ b/net/tftp.c
@@ -281,7 +281,7 @@ static void update_block_number(void)
* number of 0 this means that there was a wrap
* around of the (16 bit) counter.
*/
- if (TftpBlock == 0) {
+ if (TftpBlock == 0 && TftpLastBlock != 0) {
TftpBlockWrap++;
TftpBlockWrapOffset += TftpBlkSize * TFTP_SEQUENCE_SIZE;
TftpTimeoutCount = 0; /* we've done well, reset thhe
timeout */
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2013-08-03 10:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-03 10:09 [U-Boot] [PATCH] net: tftp: Make sure timeout will not effect wrap offset rockly
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.