The autobuild test system (on sn-devel-104) has detected an intermittent failing test in the current master tree.
The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey.sn-devel-104/2016-08-30-1020/flakey.log The samba build logs are available here: http://git.samba.org/autobuild.flakey.sn-devel-104/2016-08-30-1020/samba.stderr http://git.samba.org/autobuild.flakey.sn-devel-104/2016-08-30-1020/samba.stdout The top commit at the time of the failure was: commit 9395d958d6d5445082a369c54477e5f295df1974 Author: Volker Lendecke <[email protected]> Date: Mon Aug 29 11:35:39 2016 +0200 pthreadpool: Signal job completion without the pool mutex This essentially reverts 1c4284c7395f23. We now call an alien function from within pthreadpool, and we should not hold a mutex during that call. The alien function could (and pthreadpool_tevent_job_signal actually does) lock a mutex. We can't guarantee proper lock ordering here, so in theory we could deadlock. I haven't seen it in the wild yet, but I could imagine that both _parent pieces in pthreadpool and tevent could trigger such a deadlock. Signed-off-by: Volker Lendecke <[email protected]> Reviewed-by: Jeremy Allison <[email protected]> Autobuild-User(master): Jeremy Allison <[email protected]> Autobuild-Date(master): Tue Aug 30 04:06:20 CEST 2016 on sn-devel-144
