gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [libmicrohttpd] GNU libmicrohttpd branch master updated. 19


From: gitolite
Subject: [GNUnet-SVN] [libmicrohttpd] GNU libmicrohttpd branch master updated. 194d72e1f9628d9dd3e732ef2e199f7d4c43afd6
Date: Wed, 16 Nov 2016 10:07:38 +0100 (CET)

The branch, master has been updated
       via  194d72e1f9628d9dd3e732ef2e199f7d4c43afd6 (commit)
      from  b357bbaa6fcedfa43af7e2549535112468bde41b (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 194d72e1f9628d9dd3e732ef2e199f7d4c43afd6
Author: Christian Grothoff <address@hidden>
Date:   Wed Nov 16 10:07:36 2016 +0100

    indeed this can happen with the fast path where we call the idle handler in 
a special place just after sending the header, and thus might call it twice for 
the same connection in the same event loop run, thereby possibly entering 
cleanup twice, causing trouble; retracting FIXME

-----------------------------------------------------------------------

Summary of changes:
 src/microhttpd/connection.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/src/microhttpd/connection.c b/src/microhttpd/connection.c
index d8b0f79..e9613c4 100644
--- a/src/microhttpd/connection.c
+++ b/src/microhttpd/connection.c
@@ -2664,9 +2664,6 @@ cleanup_connection (struct MHD_Connection *connection)
 {
   struct MHD_Daemon *daemon = connection->daemon;
 
-  /* FIXME: when can this flag ever be needed? Sounds like we should
-     avoid this happening in the first place. Also, could there then
-     not be a race in this case? */
   if (connection->in_cleanup)
     return; /* Prevent double cleanup. */
   connection->in_cleanup = true;


hooks/post-receive
-- 
GNU libmicrohttpd



reply via email to

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