id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
13115	shared_mutex's exclusive_waiting_blocked may cause deadlock if readers have some dependency.	yangyihao1992@…	viboes	"I'm using boost::shared_mutex for the reader/writer. My readers have some kinds of dependency which mean Reader A will exit only after Reader B finish. At this situation, exclusive_waiting_blocked will block other readers even when there exists some readers already get the shared_lock, which cause the deadlock.

I suppose if there are readers already hold the shared_lock, other readers should be able to gain the shared_lock as well. unique_lock should exclude other readers only when all existing readers are done. Do I make sense?

Is this a semantic unclear? Any solution to fix my problem? Is there any reader-biased shared_lock in boost?"	Support Requests	closed	To Be Determined	thread	Boost 1.53.0	Regression	obsolete