ldb: Explain why an entry can vanish from the index

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>
(cherry picked from commit 9e143ee9b9f7be53c193cee3153f64c4dedc07e9)

diff --git a/lib/ldb/ldb_tdb/ldb_index.c b/lib/ldb/ldb_tdb/ldb_index.c
index 6da64cfa4ce26c7e470181a8def0de22e10f0ca0..3a1aa23aa7eaa7d7a9b3fd305e4920ab0bd281e0 100644 (file)
--- a/lib/ldb/ldb_tdb/ldb_index.c
+++ b/lib/ldb/ldb_tdb/ldb_index.c
@@ -1626,7 +1626,12 @@ static int ltdb_index_filter(struct ltdb_private *ltdb,
                                      LDB_UNPACK_DATA_FLAG_NO_DATA_ALLOC|
                                      LDB_UNPACK_DATA_FLAG_NO_VALUES_ALLOC);
                if (ret == LDB_ERR_NO_SUCH_OBJECT) {
-                       /* the record has disappeared? yes, this can happen */
+                       /*
+                        * the record has disappeared? yes, this can
+                        * happen if the entry is deleted by something
+                        * operating in the callback (not another
+                        * process, as we have a read lock)
+                        */
                        talloc_free(msg);
                        continue;
                }