From b9f32b2ea623a6ce976eb571232cdabeff160447 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Wed, 14 Jun 2017 13:57:56 +0200 Subject: [PATCH] g_lock: open with LOCK_ORDER_3 xattr_tdb needs g_lock in a clustered environment. Nobody else uses LOCK_ORDER_3 at this moment, so this looks safe. The last one to use this was dbwrap_watch.tdb, and that's gone. The only other one was notify_index.tdb, and that's gone too. Signed-off-by: Volker Lendecke Reviewed-by: Jeremy Allison --- source3/lib/g_lock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source3/lib/g_lock.c b/source3/lib/g_lock.c index 93423023822..198fe563eb9 100644 --- a/source3/lib/g_lock.c +++ b/source3/lib/g_lock.c @@ -193,7 +193,7 @@ struct g_lock_ctx *g_lock_ctx_init(TALLOC_CTX *mem_ctx, backend = db_open(result, db_path, 0, TDB_CLEAR_IF_FIRST|TDB_INCOMPATIBLE_HASH, O_RDWR|O_CREAT, 0600, - DBWRAP_LOCK_ORDER_2, + DBWRAP_LOCK_ORDER_3, DBWRAP_FLAG_NONE); TALLOC_FREE(db_path); if (backend == NULL) { -- 2.11.4.GIT