#31736: Stop using mutex_destroy(), when multiple threads can still access the mutex -------------------------------------------------+------------------------- Reporter: teor | Owner: teor Type: defect | Status: | assigned Priority: Medium | Milestone: Tor: | 0.4.2.x-final Component: Core Tor/Tor | Version: Tor: | 0.3.5.1-alpha Severity: Normal | Resolution: Keywords: consider-backport-after-042-stable, | Actual Points: 0.2 consider-backport-if-needed, diagnostics, | 042-should, 035-backport-maybe, 040-backport- | maybe, 041-backport-maybe, regression, | BugSmashFund | Parent ID: #31614 | Points: 0.2 Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by nickm):
* owner: (none) => teor * status: needs_review => assigned Comment: Hi! This all looks plausible to me at first glance. Here's another question to check on, however: * Have you thought about what happens on re-initialization? (Ideally, if Tor finishes, and then is re-initialized in the same process, we would reuse the existing mutexes rather than creating new ones. Is that achievable?) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31736#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs