Received: by 2002:a05:6359:6284:b0:131:369:b2a3 with SMTP id se4csp2458072rwb; Sun, 6 Aug 2023 19:26:10 -0700 (PDT) X-Google-Smtp-Source: AGHT+IE/gxzWvjXoNYAsc4Mni5rnfVyXzrfOx7LKCqfcuPGypOUoRIL/3cSxcJA/obPGFnriIeAF X-Received: by 2002:a05:6a21:99a1:b0:134:70b7:2386 with SMTP id ve33-20020a056a2199a100b0013470b72386mr6875791pzb.9.1691375170501; Sun, 06 Aug 2023 19:26:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691375170; cv=none; d=google.com; s=arc-20160816; b=PEMNcItireW+SbwJUSjZGW+NIQmwVTyqwrH7O6eM7KlE7GoIyjx5YI+ectHejwldvH 4AgCzddP/Evz4NbiICfh22p5H8X8BdLVe1nRqdZ0E8a9KLgpU/ElIXavIjP2r81aijSq bvCKBvIN/flSVikLm6zMv8aeKVhWMncAlf8VAiK9yO4v2V73qOlgLxnndRhlvvDlIy6H bxLa33YHPdatDQ9AC5C34niurYCcf6PV5/tqAjb6MBpbaWUW/DLeGOHuTjTnJUW8nzHF kLmMQ3NHmbIcafKn8A85tFD7oOLjgp9XB4fxMzqvffs5s8FEBBt6ML49Iqg+cKACu+65 VGfg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=jn6+lb135m0ngdu8LuNKbXLNUikB6OFg+XkaX8ko21E=; fh=exkUcuMXzigS+EIkA0N81uDLoJUubpM5wBYIPkLXhbI=; b=oX45bSI5AG3TIUeSb9qxa/6/G65P3Gpi8wx96GRJHCoGmfyI+JLAULGse6q+NgAf7g 127MxSfF/VxYd05e5/HElPEWte+svVhUrX8AmLd6efoGajR7QrO+ZnC3GcWFBrMh8Gcn Gdl0S/YFO58vWWh+mJIe9bDFMtiR67+Xjh7R7bfXS8I39b9GaBX+1Rp9iwMieujsHJmS USWWsGeK6KzbKTkSfpcEXCdVf2XFdfOY8dOAjL1Enctgxr22O7o9WFUOsTQ8Zi0Bf3GZ YSTBYThVTGaW4F0J7j35m6PZS1cs8gpkwKcQ2W0ChYdTHhcTooksM/Sv6YV6d7T5/UjW 1NNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=MF98UssL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x63-20020a638642000000b0053b8c964128si5151599pgd.708.2023.08.06.19.25.59; Sun, 06 Aug 2023 19:26:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=MF98UssL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S229686AbjHGCKN (ORCPT + 99 others); Sun, 6 Aug 2023 22:10:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229498AbjHGCKM (ORCPT ); Sun, 6 Aug 2023 22:10:12 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9CC801701 for ; Sun, 6 Aug 2023 19:10:11 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 39EB7612CC for ; Mon, 7 Aug 2023 02:10:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 67B85C433C7; Mon, 7 Aug 2023 02:10:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1691374210; bh=ANXFwJTpJlKphxqDeKAgSjzZjXGu5r3r0FIcdztZe+E=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=MF98UssLKSglr3Kpf2Ul7gIuEbn9wJdG2IHRezCKmhc+2GBGi7JXSs4PHsvHA4BQ5 XCAo3hFRXnrTYbD7CMl4O/a+B+fWkRXQWjfF6/oidwCePllkaTMijDFvYFpKQnuDyl f1mDKqvBsg0E7/5Aiob2ilUbpJrhMvHHsVqnUDjr9IZGEZ5rmRtNKg/VqvRQGG2bWM lNARj9TLJNRet90aNHD2pURX3S19fqbleZmKom5PjV/luu4s8RPZ7P9j7dRBhev30n Lo9krAe83Ciclb/m982U2T2u6aahptUHO7ktniEOBgDTUgrSERfYBqSZ+lC9hzQ+hN 9r8PXc1vosptA== Message-ID: Date: Mon, 7 Aug 2023 10:10:07 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [f2fs-dev] [PATCH] f2fs: clean up w/ sbi->log_sectors_per_block Content-Language: en-US To: Jaegeuk Kim , Shinichiro Kawasaki Cc: "linux-kernel@vger.kernel.org" , "linux-f2fs-devel@lists.sourceforge.net" , Damien Le Moal References: <20230523123521.67656-1-chao@kernel.org> From: Chao Yu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2023/8/5 3:21, Jaegeuk Kim wrote: > On 08/04, Shinichiro Kawasaki wrote: >> On May 23, 2023 / 20:35, Chao Yu wrote: >>> Use sbi->log_sectors_per_block to clean up below calculated one: >>> >>> unsigned int log_sectors_per_block = sbi->log_blocksize - SECTOR_SHIFT; >> >> Hello Chao, >> >> When I ran workloads on f2fs using v6.5-rcX with fixes [1][2] and a zoned block >> devices with 4kb logical block size, I observe mount failure as follows. When >> I revert this commit, the failure goes away. >> >> [ 167.781975][ T1555] F2FS-fs (dm-0): IO Block Size: 4 KB >> [ 167.890728][ T1555] F2FS-fs (dm-0): Found nat_bits in checkpoint >> [ 171.482588][ T1555] F2FS-fs (dm-0): Zone without valid block has non-zero write pointer. Reset the write pointer: wp[0x1300,0x8] >> [ 171.496000][ T1555] F2FS-fs (dm-0): (0) : Unaligned zone reset attempted (block 280000 + 80000) >> [ 171.505037][ T1555] F2FS-fs (dm-0): Discard zone failed: (errno=-5) >> >> The patch replaced "sbi->log_blocksize - SECTOR_SHIFT" with >> "sbi->log_sectors_per_block". However, I think these two are not equal when the >> device has 4k logical block size. The former uses Linux kernel sector size 512 >> byte. The latter use 512b sector size or 4kb sector size depending on the >> device. mkfs.f2fs obtains logical block size via BLKSSZGET ioctl from the device >> and reflects it to the value sbi->log_sector_size_per_block. This causes >> unexpected write pointer calculations in check_zone_write_pointer(). This >> resulted in unexpected zone reset and the mount failure. >> >> I think this patch needs revert. What do you think? > > Yeah, applied the revert. Jaegeuk, could you please send the patch to mailing list? Thanks, > >> >> [1] https://lkml.kernel.org/linux-f2fs-devel/20230711050101.GA19128@lst.de/ >> [2] https://lore.kernel.org/linux-f2fs-devel/20230804091556.2372567-1-shinichiro.kawasaki@wdc.com/