mirror of
https://github.com/samba-team/samba.git
synced 2025-02-02 09:47:23 +03:00
cba169252e
It means that in callers function will run under a single tdb chainlock, which means callers from the outside will never see the record being locked at g_lock level, as the g_lock is only held in memory. within the single tdb chainlock. As a result we'll very unlikely hit the case where we need to wait for a g_lock using the dbwrap_watch logic. Review with: git show -w BUG: https://bugzilla.samba.org/show_bug.cgi?id=15125 Signed-off-by: Stefan Metzmacher <metze@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org>