summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-11-16 16:23:15 -0500
committerNick Mathewson <nickm@torproject.org>2011-11-16 16:23:15 -0500
commit2f3dad10a8db72fddd797f39a72c34e64cf3837f (patch)
tree9fc9361bdea4b06f3a0da9308060bb0c7dbfb54b
parent8200a85323289f98a54b2a5293672cce8ddc5a2c (diff)
parent7be50c26e8b2ec0bd0121d5e8b2dc55de977cf5a (diff)
downloadtor-2f3dad10a8db72fddd797f39a72c34e64cf3837f.tar.gz
tor-2f3dad10a8db72fddd797f39a72c34e64cf3837f.zip
Merge branch 'bug4457_master'
-rw-r--r--changes/bug44579
-rw-r--r--changes/bug4457_master6
-rw-r--r--src/common/compat_libevent.c43
3 files changed, 57 insertions, 1 deletions
diff --git a/changes/bug4457 b/changes/bug4457
new file mode 100644
index 0000000000..fe7c95ff80
--- /dev/null
+++ b/changes/bug4457
@@ -0,0 +1,9 @@
+ o Minor bugfixes:
+ - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
+ that it doesn't attempt to allocate a socketpair. This could cause
+ some problems on windows systems with overzealous firewalls. Fix for
+ bug 4457; workaround for Libevent versions 2.0.1-alpha through
+ 2.0.15-stable.
+
+ - Detect failure to initialize Libevent. Better detection for bug 4457.
+
diff --git a/changes/bug4457_master b/changes/bug4457_master
new file mode 100644
index 0000000000..d394643b6d
--- /dev/null
+++ b/changes/bug4457_master
@@ -0,0 +1,6 @@
+ o Minor features:
+ - When we fail to initialize Libevent, retry with IOCP disabled so we
+ don't need to turn on multi-threading support in Libevent, which in
+ turn requires a working socketpair(). This is a workaround for bug
+ 4457, which affects Libevent versions from 2.0.1-alpha through
+ 2.0.15-stable.
diff --git a/src/common/compat_libevent.c b/src/common/compat_libevent.c
index 3201738701..7a28c9bc9b 100644
--- a/src/common/compat_libevent.c
+++ b/src/common/compat_libevent.c
@@ -195,16 +195,33 @@ tor_libevent_initialize(tor_libevent_cfg *torcfg)
#ifdef HAVE_EVENT2_EVENT_H
{
- struct event_config *cfg = event_config_new();
+ int attempts = 0;
+ int using_threads;
+ struct event_config *cfg;
+
+ retry:
+ ++attempts;
+ using_threads = 0;
+ cfg = event_config_new();
+ tor_assert(cfg);
#if defined(MS_WINDOWS) && defined(USE_BUFFEREVENTS)
if (! torcfg->disable_iocp) {
evthread_use_windows_threads();
event_config_set_flag(cfg, EVENT_BASE_FLAG_STARTUP_IOCP);
using_iocp_bufferevents = 1;
+ using_threads = 1;
+ } else {
+ using_iocp_bufferevents = 0;
}
#endif
+ if (!using_threads) {
+ /* Telling Libevent not to try to turn locking on can avoid a needless
+ * socketpair() attempt. */
+ event_config_set_flag(cfg, EVENT_BASE_FLAG_NOLOCK);
+ }
+
#if defined(LIBEVENT_VERSION_NUMBER) && LIBEVENT_VERSION_NUMBER >= V(2,0,7)
if (torcfg->num_cpus > 0)
event_config_set_num_cpus_hint(cfg, torcfg->num_cpus);
@@ -219,11 +236,35 @@ tor_libevent_initialize(tor_libevent_cfg *torcfg)
the_event_base = event_base_new_with_config(cfg);
event_config_free(cfg);
+
+ if (using_threads && the_event_base == NULL && attempts < 2) {
+ /* This could be a socketpair() failure, which can happen sometimes on
+ * windows boxes with obnoxious firewall rules. Downgrade and try
+ * again. */
+#if defined(MS_WINDOWS) && defined(USE_BUFFEREVENTS)
+ if (torcfg->disable_iocp == 0) {
+ log_warn(LD_GENERAL, "Unable to initialize Libevent. Trying again with "
+ "IOCP disabled.");
+ } else
+#endif
+ {
+ log_warn(LD_GENERAL, "Unable to initialize Libevent. Trying again.");
+ }
+
+ torcfg->disable_iocp = 1;
+ goto retry;
+ }
+
}
#else
the_event_base = event_init();
#endif
+ if (!the_event_base) {
+ log_err(LD_GENERAL, "Unable to initialize Libevent: cannot continue.");
+ exit(1);
+ }
+
#if defined(HAVE_EVENT_GET_VERSION) && defined(HAVE_EVENT_GET_METHOD)
/* Making this a NOTICE for now so we can link bugs to a libevent versions
* or methods better. */