Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp6272ybt; Tue, 23 Jun 2020 13:49:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxZXleZHbbNfO88s7JMTz1+EM6016z4RX8ekMX9Aou6PCSiPJZilCgyeEFtri8VFPxFjW14 X-Received: by 2002:a17:906:dbda:: with SMTP id yc26mr21368084ejb.82.1592945347901; Tue, 23 Jun 2020 13:49:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592945347; cv=none; d=google.com; s=arc-20160816; b=XjKbEGa5FMhrTERaMpx8Vuvs/OT0bc/SHwNuKDdRAksL1Qp2wlMpKbe9mtiqLNATz2 ivU4MHK9XpiISPQBqlXK077KRNPdc8y2wQExPwugx2TaMf69IQmHoaV+pEA0gw+4Ifzr ndkl5m1zYz9wx5HEGthqkB5OaSY3A2kvd5MDArRxNoRwSO1huDz91QKjAiIehRFq/RLV EysWhdl9A40lUA3f3Q2xG5XkSBy78UeD/8KzznfcOZVKTa8eAM2NjL3WfGCpxv45rytd 9ZtMOHzH4N0Arx35EJ8KIRA4SsGUp+YXFc57K9FxOpSqBw0rrUk/8vJvbiMYw0qWJ7Vt uw2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=7t2AoxUHecpzwFYvur9ZS50XtdpxvlkCXkNYX1JFx4w=; b=xI072dMatAUUcsExOtPmyNOO2Y+N3oyoBFPzmUpu7Jr+meLsPyeha78jMH07xmZYra 05MxRpeaJeKFhrRzPrrAc5QA9M7Jr/mDn7V2tPLUsAnVKCJw0v4SmzIvdfozXMuLG85w rlNxzJ+TsT73OuQaXTRjES4V9M2zCFQ2ZYLm5WS8UFbagEsYnr9bZdXdEuf9ATJbUNvQ uQBmUbj2PmYaw/Wg45I5NLP7qgoYO+Wq7+CSjZ7qrQ7FRruu9ejhxYHwmfS3siokOvHI xFXnzWQnZff9JfZanndleVVnROo57Y7hv12HPMJDHFN0Zi88kQd/EbJWAUDN32vjOu/n sUWg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SXe30Odj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d18si11569498edz.309.2020.06.23.13.48.44; Tue, 23 Jun 2020 13:49:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SXe30Odj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391860AbgFWUrS (ORCPT + 99 others); Tue, 23 Jun 2020 16:47:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:45296 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2392634AbgFWUrB (ORCPT ); Tue, 23 Jun 2020 16:47:01 -0400 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 6A11F214DB; Tue, 23 Jun 2020 20:47:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592945222; bh=dgYiHx/8l9R33fw+vlvYho62cYUh2ayEQV1E/YH40C0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SXe30OdjiGTh9+yZz98WLTK3Um9OFS5kawpYj7hnZnbvsFEoP04vkYJwIeCQy0Orq mIywH2ZqMB+D+R32Bn3SdWlSwh6xtyfYihgJ0fsFM8Bd0arllh48Ay7npu7rzGtYY+ BregfcgCduu6Q5XrYUBfVY1hPb93Smfg4zhqBBDs= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Bob Peterson , Andreas Gruenbacher , Sasha Levin Subject: [PATCH 4.14 086/136] gfs2: Allow lock_nolock mount to specify jid=X Date: Tue, 23 Jun 2020 21:59:02 +0200 Message-Id: <20200623195308.016767362@linuxfoundation.org> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20200623195303.601828702@linuxfoundation.org> References: <20200623195303.601828702@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: Bob Peterson [ Upstream commit ea22eee4e6027d8927099de344f7fff43c507ef9 ] Before this patch, a simple typo accidentally added \n to the jid= string for lock_nolock mounts. This made it impossible to mount a gfs2 file system with a journal other than journal0. Thus: mount -tgfs2 -o hostdata="jid=1" Resulted in: mount: wrong fs type, bad option, bad superblock on In most cases this is not a problem. However, for debugging and testing purposes we sometimes want to test the integrity of other journals. This patch removes the unnecessary \n and thus allows lock_nolock users to specify an alternate journal. Signed-off-by: Bob Peterson Signed-off-by: Andreas Gruenbacher Signed-off-by: Sasha Levin --- fs/gfs2/ops_fstype.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c index 057be88eb1b42..7ed0359ebac61 100644 --- a/fs/gfs2/ops_fstype.c +++ b/fs/gfs2/ops_fstype.c @@ -922,7 +922,7 @@ fail: } static const match_table_t nolock_tokens = { - { Opt_jid, "jid=%d\n", }, + { Opt_jid, "jid=%d", }, { Opt_err, NULL }, }; -- 2.25.1