summaryrefslogtreecommitdiffstats
path: root/src/dbus/dbus_minimal_p.h
diff options
context:
space:
mode:
authorMÃ¥rten Nordheim <marten.nordheim@qt.io>2019-08-13 15:17:40 +0200
committerMarc Mutz <marc.mutz@kdab.com>2019-08-16 20:47:33 +0000
commit6d3a4546934827955f0eb2b07a9928f82790ba37 (patch)
treeb72129a7ac89b2c12d38a575907a4a7c64dc2023 /src/dbus/dbus_minimal_p.h
parent0d81667f87e80f7d0a866df3b0ee4a164f47e26d (diff)
DBus: fix deadlock when destroying QDBusServer
Observed infrequently in the QDBus tests, it would deadlock when destroying QDBusServer at the same time as qDBusNewConnection was being executed as they were locking the same locks, but in opposite order. QDBusServer locks d->lock, then QDBusConnectionManager::instance()->mutex. While qDBusNewConnection locks QDBusConnectionManager::instance()->mutex, then serverConnection->lock (and serverConnection here is QDBusServer's d-pointer). QOrderedMutexLocker cannot be used in this situation because it operates on QMutex*, which d->lock (QReadWriteLock) is not. Change the code to lock QDBusConnectionManager's mutex before d->lock and then unlock the QMutexLocker where it would previously destruct. If QDBusConnectionManager has already been destroyed then we pass a nullptr to the QMutexLocker which is fine and will not do anything. Fixes: QTBUG-74635 Change-Id: I7f02d7759da67377996ef042c81b0969ccb8aadb Reviewed-by: Marc Mutz <marc.mutz@kdab.com> Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Diffstat (limited to 'src/dbus/dbus_minimal_p.h')
0 files changed, 0 insertions, 0 deletions