I saw systems with locking.tdb records being part of: ctdb catdb smbXsrv_tcon_global.tdb It's yet unknown how that happened, but we should not panic in srvsvc_* calls because the info0 pointer was NULL.
This bug was referenced in samba master: 00bab5b3c821f272153a25ded9743460887a7907
Created attachment 16674 [details] Patch for v4-14-test
Created attachment 16675 [details] Patch for v4-13-test
(In reply to Stefan Metzmacher from comment #3) Pushed to autobuild-v4-{14,13}-test.
This bug was referenced in samba v4-14-test: 8f7ab597969e6e834ef333d5cf314f770325d6a9
This bug was referenced in samba v4-14-stable (Release samba-4.14.6): 8f7ab597969e6e834ef333d5cf314f770325d6a9
This bug was referenced in samba v4-13-test: b9b1d98af4c7cd2326e12e1c3b734056663932d1
This bug was referenced in samba v4-13-stable (Release samba-4.13.10): b9b1d98af4c7cd2326e12e1c3b734056663932d1
Closing out bug report. Thanks!