From 26932271a85a08a755c81df0138d770b6a3bc3a3 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Mon, 22 May 2017 16:00:08 +0200 Subject: smbd: Claim version in g_lock Protect smbd against version incompatibilities in a cluster. At first startup smbd locks "samba_version_string" and writes its version string. It then downgrades the lock to a read lock. Subsequent smbds check against the version string and also keep the read lock around. If the version does not match, we try to write our own version. But as there's a read lock, the lock upgrade to write lock will fail due the read lock being around. So as long as there's one smbd with this read lock, no other version of smbd will be able to start. Signed-off-by: Volker Lendecke Reviewed-by: Jeremy Allison --- docs-xml/smbdotconf/misc/allowunsafeclusterupgrade.xml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 docs-xml/smbdotconf/misc/allowunsafeclusterupgrade.xml (limited to 'docs-xml') diff --git a/docs-xml/smbdotconf/misc/allowunsafeclusterupgrade.xml b/docs-xml/smbdotconf/misc/allowunsafeclusterupgrade.xml new file mode 100644 index 00000000000..02398ff2c95 --- /dev/null +++ b/docs-xml/smbdotconf/misc/allowunsafeclusterupgrade.xml @@ -0,0 +1,16 @@ + + + If set to no (the default), smbd checks at startup if + other smbd versions are running in the cluster and refuses to + start if so. This is done to protect data corruption in + internal data structures due to incompatible Samba versions + running concurrently in the same cluster. Setting this + parameter to yes disables this + safety check. + + +no + -- cgit v1.2.1