nodedev: Signal initCond with driver locked
nodedev: Signal initCond with driver locked

This is more academic dispute than a real bug, but this is taken
from pthread_cond_broadcast(3p) man:

  The pthread_cond_broadcast() or pthread_cond_signal() functions
  may be called by a thread whether or not it currently owns the
  mutex that threads calling pthread_cond_wait() or
  pthread_cond_timedwait() have associated with the condition
  variable during their waits; however, if predictable scheduling
  behavior is required, then that mutex shall be locked by the
  thread calling pthread_cond_broadcast() or
  pthread_cond_signal().

Therefore, broadcast the initCond while the nodedev driver is
still locked.

Signed-off-by: Michal Privoznik <83d82aaba2eed257f4814b0c239c260c4caaadf0@redhat.com>
Reviewed-by: Erik Skultety <2c14d38fa47c8799f1b9c16280abe27f8edfec6e@redhat.com>

jfehlig/libvirt,crobinso/libvirt,zippy2/libvirt,crobinso/libvirt,olafhering/libvirt,jfehlig/libvirt,olafhering/libvirt,zippy2/libvirt,crobinso/libvirt,nertpinx/libvirt,jfehlig/libvirt,nertpinx/libvirt,jfehlig/libvirt,nertpinx/libvirt,libvirt/libvirt,zippy2/libvirt,libvirt/libvirt,zippy2/libvirt,crobinso/libvirt,nertpinx/libvirt,libvirt/libvirt,olafhering/libvirt,nertpinx/libvirt,libvirt/libvirt,olafhering/libvirt