Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp3143627pxb; Tue, 24 Aug 2021 16:37:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzko9XHdhxyWjdiPjvRR7cujhEyxgAWQKOaWZOlktXaen5Tn6rg0ZBcHFp82a3yJ6hhQrwz X-Received: by 2002:a17:906:e82:: with SMTP id p2mr19137082ejf.50.1629848251579; Tue, 24 Aug 2021 16:37:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629848251; cv=none; d=google.com; s=arc-20160816; b=l7giN7+SC3YIjyeyfhbqUMxQRmPLUAEVrGcJ7Q0mFvHX/waoMFnWXhydfOI97T0Fvy Uq3yyhCzN2wfDd8NG7N4/1xUs9ItC9d0LVIlEB6lSsnrg8aI7zJO29W59DBF6yiDyda4 QqKpqKD0vkfiQHvoI18WELPF9A13jk5tqMoeoWkPAU8nOzWv0vlEIJsTA/IYWhHWQa30 5O4kM4qA9CJuXg7el78KsaNkWoO9tUHmz1ijZcsVq8V3c2HXY8qKrIJtPYrTqedbbnxN zArUo7kxQzpnksako575HEa0CIX5VdrOW0wjBThD1nLul8KbkkBba2/BvZliuA3GJBeY E8CA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=MHiIl+s0jgnoQOB/PYq1mrWodylRXWxCj/sxy9Vjjug=; b=uWqXmJvWvra76TSeYZqR8puWqPy3b/gJylg87Z5tdoO4OhMuVJmsdxVCtX1v0WeleW fBOEavSw/wrTacPrQGAFbL4fGUQeBe7qFiLltNHOkc3ApmeVzo/8IYUnxUpt9UHHofd0 IWW2HLnxEuZEvFtzg+sSig/uSokN8ZnbOHzGPs+Cyirl/84TkNcv5mQiKhIiuLDN6MsW 6ET1PAoN7AQU3fwO6UyP+k8tCI4s2rbVwOw/+Q2ctF6klVoiZDXVx6DSt8fZwTTjlIJC cw14FLwJwfr5lor90ht4KoPSp6QJC02lqZdXuMOCyVJrvJHCIgiogMTQbyYRz1u4zlZq BR/w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Xa5ffoXs; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e12si17633237ejk.703.2021.08.24.16.37.00; Tue, 24 Aug 2021 16:37:31 -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=k20201202 header.b=Xa5ffoXs; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235085AbhHXXgZ (ORCPT + 99 others); Tue, 24 Aug 2021 19:36:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:55738 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234775AbhHXXgU (ORCPT ); Tue, 24 Aug 2021 19:36:20 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 842C261101; Tue, 24 Aug 2021 23:35:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1629848135; bh=TmmmCy3ttRTPrwcFEXqnLiJzYlTQBbSyZZokMksdh6k=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Xa5ffoXsFfxhlL30GG+vlyO9U4ExCvHxDy3AoC5wlWqluFeDCgQHKS36MWFQ56jXT BuuB1dJ0va2BlhoHRFV6WCYVGLi4ti6P3ct0fK6nkmJVUgteaC1dxWbZCBU3Ve1AAb URsvWYx9ZRP5DK6KL76/uxZ1F6TKIKf3r8WppEZE4H3PAD/vH/Y7nSnii/cEVRvKtW aQ3tCjlsW4Srh4+JD3slxikZUXhuD0bDPXQTQuYYxt3QlpSOnGZVsnnz2NrogkCISD BBtkT1JUx2VZMtw+CMukdigpldZvGfQ/W5yXg1U6qZtbYtbV2MLVxTFi33/fC30uSN YQtL/bPT6T2oQ== Subject: Re: [PATCH] f2fs: fix wrong option name printed by parse_options() To: Jaegeuk Kim Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Chao Yu References: <20210824011948.15408-1-chao@kernel.org> From: Chao Yu Message-ID: <2520fdb0-835f-2664-198b-386416464e0d@kernel.org> Date: Wed, 25 Aug 2021 07:35:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/8/25 1:26, Jaegeuk Kim wrote: > On 08/24, Chao Yu wrote: >> It prints below kernel message during mounting w/ checkpoint=disable >> option: >> >> "F2FS-fs (pmem0): checkpoint=merge cannot be used with checkpoint=disable" >> >> Fix typo "checkpoint=merge" w/ "checkpoint_merge" >> >> Signed-off-by: Chao Yu >> --- >> fs/f2fs/super.c | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c >> index 49e153fd8183..88c66e46bd5c 100644 >> --- a/fs/f2fs/super.c >> +++ b/fs/f2fs/super.c >> @@ -1289,6 +1289,12 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount) >> return -EINVAL; >> } >> >> + if (test_opt(sbi, DISABLE_CHECKPOINT) && >> + test_opt(sbi, MERGE_CHECKPOINT)) { >> + f2fs_err(sbi, "checkpoint_merge cannot be used with checkpoint=disable\n"); >> + return -EINVAL; > > What about disabling MERGE_CHECKPOINT autmatically? checkpoint_merge was introduced separately rather than adding a new "merge" parameter in mount option "checkpoint=%s", so they are compatible. Please ignore this patch... Thanks, > >> + } >> + >> /* Not pass down write hints if the number of active logs is lesser >> * than NR_CURSEG_PERSIST_TYPE. >> */ >> -- >> 2.32.0