[Top][All Lists]

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

[lwip-commits] [SCM] lwIP - A Lightweight TCPIP stack branch, master, up

From: Joel Cunningham
Subject: [lwip-commits] [SCM] lwIP - A Lightweight TCPIP stack branch, master, updated. 5030fa81a020280c467126568027608fa08e5136
Date: Wed, 23 Nov 2016 21:06:16 +0000 (UTC)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lwIP - A Lightweight TCPIP stack".

The branch, master has been updated
       via  5030fa81a020280c467126568027608fa08e5136 (commit)
      from  0f87cb92b82b183d81175b2f5b58904157c92acb (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5030fa81a020280c467126568027608fa08e5136
Author: Joel Cunningham <address@hidden>
Date:   Wed Nov 23 09:45:38 2016 -0600

    bug #49684, api_msg: treat non-blocking ERR_MEM as ERR_WOULDBLOCK
    This corrects a case in lwip_netconn_do_writemore() where if a
    non-blocking socket receives ERR_MEM in a call to tcp_write(), it would
    return ERR_MEM, which would result in ENOMEM coming out of the socket
    This case can be gracefully handled by returning ERR_WOULDBLOCK since the
    socket is already marked as no longer writable and sent_tcp/poll_tcp will
    mark the socket as writable again based on available buffer space
    This is very similiar to how ERR_MEM is resolved for blocking sockets


Summary of changes:
 src/api/api_msg.c |   14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

lwIP - A Lightweight TCPIP stack

reply via email to

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