[gPXE-devel] [PATCHv2] [tcp core] Wait for TCP to safely close
Guo-Fu Tseng
cooldavid at cooldavid.org
Thu Jul 15 12:13:45 EDT 2010
On Thu, 15 Jul 2010 13:18:05 +0800, cooldavid wrote
> After some discussion with Piotr and Michael, I think it might
> be an acceptable solution for the issue that gPXE leaves remote
> peer TCP in undesired state.
>
> The reason I don't mark activity_start at somewhere like tcp_open
> or ESTABLISHED is that sanboot do not close the TCP connection
> before hand of the control to OS.
>
> Signed-off-by: Guo-Fu Tseng <cooldavid at cooldavid.org>
> ---
> src/core/activity.c | 64 +++++++++++++++++++++++++++++++++++++++++++
> src/core/image.c | 8 +++++
> src/core/main.c | 2 +
> src/include/gpxe/activity.h | 28 +++++++++++++++++++
> src/include/gpxe/tcp.h | 13 +++++++++
> src/net/tcp.c | 16 +++++++++++
> src/usr/autoboot.c | 6 ++++
> 7 files changed, 137 insertions(+), 0 deletions(-)
> create mode 100644 src/core/activity.c
> create mode 100644 src/include/gpxe/activity.h
I've merged this patch into the latest
[PATCHv3 0/7] [tcp] Several TCP fixes
patch series.
Guo-Fu Tseng
More information about the gPXE-devel
mailing list