lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #48543] TCP sent callback may prematurely report sent


From: Ambroz Bizjak
Subject: [lwip-devel] [bug #48543] TCP sent callback may prematurely report sent data when only part of a segment is acked
Date: Tue, 19 Jul 2016 20:11:07 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Follow-up Comment #5, bug #48543 (project lwip):

I suppose there are some situations which could lead to a crash. Say the
segment is composed of multiple chained pbufs (due to multiple tcp_write
calls), and the application free()s the buffer referenced by the first pbuf
since the data has supposedly been acked. But lwip then tries to retransmit
the whole segment. On a platform with a free() that works with paging /
virtual memory, the freed data might actually become inaccessible causing a
crash.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?48543>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]