Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1523539yba; Thu, 25 Apr 2019 00:57:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqwH0YvhM3qOzU09Dd/yBtOcJ8Zfl2+xI8agQT7Lhnd+trnMIkmEVT9byY08zczf/KIJjT8+ X-Received: by 2002:a17:902:a706:: with SMTP id w6mr37489298plq.91.1556179050270; Thu, 25 Apr 2019 00:57:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556179050; cv=none; d=google.com; s=arc-20160816; b=aaHsH4LEYYHmSGeKaRdIz37+HXKsKjZP4mR7CX2Q9pVqoPMMW1YKp1aYmqswNu1JFK Rvls/BZJB/8gkrmahU6Jynv849f8+M4AEWRnlpyoXebVBvjClDeNn1kfGD9Cy473Q2WI 1WWV2Twg4fxD1aHeWTSYploVYTSRoMiAVNAqEgwhGW5xlRA65OTgx9tf/o/W82iJCdBT 6foe7iph7XpbbcCuzdWpoizCFbpeQKJWq1c2QpGonrCrfhyrp6uji7DVascGFmu00jfu pzKTj0SCDVkLLuYmxfp868hhgwqvLVfJIELInX3kVU7q3yBIIm5An9kE8F/2kPN1HHr2 woSA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=jPxiPum4MOo8yOydwmqLxA/3TL6QN9xrVJpSz+esyKo=; b=a7YgEziCXoOmNouYz4zy1bW/ET/gB0WE+/hp9PmiFrDPBn1IvmL0h8J2mMYy1sBFKH FdeK1hKZII5Lp04KMWkaD3r6P/rfNy1yG7KeUR4fFfZf+Rl3fOGP9HwM3UuyeF4hXAkl BWLLbHfxUu9svBk4V8pvEicMRUNASkdo1x/9afJVMK7PwcmRopXL2YlEvjTi14QPuDEx 2Uh7DCu2Qn4nq0GpCB48S8OWN97aydf5GnIJuxq35NovcboQqeRmmurm4z7wsl4jphCi Cx+krgMacYzKG4cpZGmxwly1yjIgvtnuEZnH+x/iinUqRx6OOCOYfnJJTCxgM30WgeaU M5Ig== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p85si22051553pfi.27.2019.04.25.00.57.15; Thu, 25 Apr 2019 00:57:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388086AbfDYBgx (ORCPT + 99 others); Wed, 24 Apr 2019 21:36:53 -0400 Received: from szxga08-in.huawei.com ([45.249.212.255]:33014 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728775AbfDYBgw (ORCPT ); Wed, 24 Apr 2019 21:36:52 -0400 Received: from DGGEMM401-HUB.china.huawei.com (unknown [172.30.72.53]) by Forcepoint Email with ESMTP id AD685A898FA635AAC9C9; Thu, 25 Apr 2019 09:36:49 +0800 (CST) Received: from dggeme763-chm.china.huawei.com (10.3.19.109) by DGGEMM401-HUB.china.huawei.com (10.3.20.209) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 25 Apr 2019 09:36:49 +0800 Received: from [10.134.22.195] (10.134.22.195) by dggeme763-chm.china.huawei.com (10.3.19.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Thu, 25 Apr 2019 09:36:48 +0800 Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: relocate chksum_offset for large_nat_bitmap feature To: Ju Hyung Park CC: Jaegeuk Kim , , References: <20190422093353.61014-1-yuchao0@huawei.com> <20190422093353.61014-2-yuchao0@huawei.com> From: Chao Yu Message-ID: Date: Thu, 25 Apr 2019 09:36:49 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.134.22.195] X-ClientProxiedBy: dggeme715-chm.china.huawei.com (10.1.199.111) To dggeme763-chm.china.huawei.com (10.3.19.109) X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ju Hyung, On 2019/4/24 19:43, Ju Hyung Park wrote: > Hi Chao, > > On Mon, Apr 22, 2019 at 6:34 PM Chao Yu wrote: >> + if (__is_set_ckpt_flags(*cp_block, CP_LARGE_NAT_BITMAP_FLAG)) { >> + if (crc_offset != CP_MIN_CHKSUM_OFFSET) { >> + f2fs_put_page(*cp_page, 1); >> + f2fs_msg(sbi->sb, KERN_WARNING, >> + "layout of large_nat_bitmap is deprecated, " >> + "run fsck to repair, chksum_offset: %zu", >> + crc_offset); >> + return -EINVAL; >> + } >> + } >> + > > I try not to be a Grammar Nazi and a jerk on every patches, but since > this is a message a user would directly encounter, I'd like to see a > bit less ambiguous message. Please feel free to give us your opinion or suggestion. :) > > How about "using deprecated layout of large_nat_bitmap, please run > fsck v1.13.0 or higher to repair, chksum_offset: %zu"? > The original message seems to suggest that large_nat_bitmap is > deprecated outright. > > Also, I'd like to suggest to write down an actual version of > f2fs-tools here as we've seen older versions of fsck doing even more > damage and the users might not have the latest f2fs-tools installed. Agreed, user should be told which version of fsck can repair that problem, will update the message in next version. > > Btw, what happens if we use the latest fsck to fix the corrupted image > and use the older kernel to mount it? > Would it even mount? No, since fixed image is using a new layout, how about giving the detailed information about which version of kernel user should update to, once we detect such issue and trigger the repairing? Thanks, > > Thanks. > . >