potential deadlock?

Michael Teske via omniORB-list <[email protected]> Tue, 24 Oct 2017 10:32:35 +0200

Newsgroups	gmane.comp.corba.omniorb.user
Message-ID	<[email protected]>

Hi,

don't know if this is really a problem, but I recently ran a program of
mine with TSAN thread-sanitizer and it found this lock-order-inversion
(potential deadlock) in omniorb:

SocketCollection::Select holds pd_collection_lock
(if count >0 in line 269)
and calls notifyReadable (line 315)
which may call giopServer::notifyRzReadable
which wants pd_lock

versus

giopServer::instantiate holds pd_lock
and calls tcpEndpoint::Bind()
which calls SocketCollection::addSocket
which wants pd_collection_lock

Maybe it's not a real problem because giopServer::instantiate is called
only on creation time, but I though I'd let you know.

Greetings,
  Michael

_______________________________________________
omniORB-list mailing list
[email protected]
http://www.omniorb-support.com/mailman/listinfo/omniorb-list