From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DEFCBC43603 for ; Wed, 11 Dec 2019 15:50:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A904F2073B for ; Wed, 11 Dec 2019 15:50:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576079436; bh=pfK74v3YmtA8H49th10aE3QUou3ru2WOeyG21yIhRK8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=siKjaHjb1rl3XG6NEGE8+1BHM4qhuu7Y5qFMM8410XZqRtk6vWh5u6TfnyAbfDW7/ cIixSDzy7VDtAfufSGv1TIOWvEJXDANgxopwr4cBUcBLopivtotVYMVfzdyqIs4nUq uyaOEBK7uFi0RyQaxBWtPR+s3LvyIjikOK5y+fSg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732498AbfLKPXB (ORCPT ); Wed, 11 Dec 2019 10:23:01 -0500 Received: from mail.kernel.org ([198.145.29.99]:53778 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732311AbfLKPW5 (ORCPT ); Wed, 11 Dec 2019 10:22:57 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3D8BA2073D; Wed, 11 Dec 2019 15:22:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576077776; bh=pfK74v3YmtA8H49th10aE3QUou3ru2WOeyG21yIhRK8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=1N245TRkyTHPinFymACc36oM4Gni2waSXu+OSVAu5jOdrVIFGuJ0Rg7wh4Cn6cjr/ IB9H72GoMZT5b7GC+L+/hi8s6SPiyuBH9rcoD9vLFjeBJDnOdhU2ciK7TCfoHHoAC0 tRRVwgzQXwBEqcrJLYNSDHcg7nU78QOCCJiM0k6g= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, David Teigland , Sasha Levin Subject: [PATCH 4.19 167/243] dlm: fix invalid cluster name warning Date: Wed, 11 Dec 2019 16:05:29 +0100 Message-Id: <20191211150350.457147152@linuxfoundation.org> X-Mailer: git-send-email 2.24.1 In-Reply-To: <20191211150339.185439726@linuxfoundation.org> References: <20191211150339.185439726@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: David Teigland [ Upstream commit 3595c559326d0b660bb088a88e22e0ca630a0e35 ] The warning added in commit 3b0e761ba83 "dlm: print log message when cluster name is not set" did not account for the fact that lockspaces created from userland do not supply a cluster name, so bogus warnings are printed every time a userland lockspace is created. Signed-off-by: David Teigland Signed-off-by: Sasha Levin --- fs/dlm/user.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/dlm/user.c b/fs/dlm/user.c index 13f29409600bb..3c84c62dadb7b 100644 --- a/fs/dlm/user.c +++ b/fs/dlm/user.c @@ -25,6 +25,7 @@ #include "lvb_table.h" #include "user.h" #include "ast.h" +#include "config.h" static const char name_prefix[] = "dlm"; static const struct file_operations device_fops; @@ -404,7 +405,7 @@ static int device_create_lockspace(struct dlm_lspace_params *params) if (!capable(CAP_SYS_ADMIN)) return -EPERM; - error = dlm_new_lockspace(params->name, NULL, params->flags, + error = dlm_new_lockspace(params->name, dlm_config.ci_cluster_name, params->flags, DLM_USER_LVB_LEN, NULL, NULL, NULL, &lockspace); if (error) -- 2.20.1