s3:registry: implement values_need_update and subkeys_need_update in the smbconf...

It simply calls to the regdb functions.
This fixes a caching issue uncovered by recent changes.
(cherry picked from commit bff7589818e602ace6cd0a4125d5f6a2ba97cded)
(cherry picked from commit f2ab0372049f839c9201bc326030163996dec769)

diff --git a/source3/registry/reg_backend_smbconf.c b/source3/registry/reg_backend_smbconf.c
index 912f5eb1bf636af70fd38412cf67ac680e69ca99..44ffd42fedaadc6c3a7ec8d04b903cc4de652edd 100644 (file)
--- a/source3/registry/reg_backend_smbconf.c
+++ b/source3/registry/reg_backend_smbconf.c
@@ -81,6 +81,15 @@ static WERROR smbconf_set_secdesc(const char *key,
        return regdb_ops.set_secdesc(key, secdesc);
 }
 
+static bool smbconf_subkeys_need_update(struct regsubkey_ctr *subkeys)
+{
+       return regdb_ops.subkeys_need_update(subkeys);
+}
+
+static bool smbconf_values_need_update(struct regval_ctr *values)
+{
+       return regdb_ops.values_need_update(values);
+}
 
 /*
  * Table of function pointers for accessing smb.conf data
@@ -96,4 +105,6 @@ struct registry_ops smbconf_reg_ops = {
        .reg_access_check = smbconf_reg_access_check,
        .get_secdesc = smbconf_get_secdesc,
        .set_secdesc = smbconf_set_secdesc,
+       .subkeys_need_update = smbconf_subkeys_need_update,
+       .values_need_update = smbconf_values_need_update,
 };