wurms gitweb - mono.git/commit

author	Ludovic Henry <ludovic@xamarin.com>
	Wed, 9 Nov 2016 20:59:36 +0000 (15:59 -0500)
committer	GitHub <noreply@github.com>
	Wed, 9 Nov 2016 20:59:36 +0000 (15:59 -0500)
commit	38a348c991049fb0134e27774292c2d8929fda22
tree	63f5490bf98d588c1718aab3ad046980dc14addf	tree \| snapshot
parent	723e5a1b07db0f4d83c01bf41e8e6120ea86b3b5	commit \| diff

[threads] Always use the `suspended` MonoOSEvent for self-suspend (#3915)

* [stw] Refactor to treat error/success cases first

* [threads] Always use the `suspended` MonoOSEvent for self-suspend

The previous self-suspend mechanism was inherently racy:
- T1 self suspend:
- T1 calls mono_thread_info_begin_self_suspend, but doesn't call mono_thread_info_end_self_suspend yet
- T2 suspends T1 <-- the suspend_count is > 0, trigerring the assertion at mono-threads.c:184

my mono mirror. check out Moved to http://github.com/mono/mono

RSS Atom

mcs/class/corlib/System.Threading/Thread.cs		diff \| blob \| history
mcs/class/corlib/System/Environment.cs		diff \| blob \| history
mono/metadata/appdomain.c		diff \| blob \| history
mono/metadata/object-internals.h		diff \| blob \| history
mono/metadata/sgen-stw.c		diff \| blob \| history
mono/metadata/threads.c		diff \| blob \| history
mono/tests/Makefile.am		diff \| blob \| history
mono/tests/thread-suspend-selfsuspended.cs	[new file with mode: 0644]	blob
mono/utils/mono-threads-state-machine.c		diff \| blob \| history
mono/utils/mono-threads.c		diff \| blob \| history
mono/utils/mono-threads.h		diff \| blob \| history