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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D414C77B61 for ; Thu, 13 Apr 2023 23:40:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230172AbjDMXk1 (ORCPT ); Thu, 13 Apr 2023 19:40:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34378 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229656AbjDMXkW (ORCPT ); Thu, 13 Apr 2023 19:40:22 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 41EBEDF for ; Thu, 13 Apr 2023 16:40:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B1C8A64282 for ; Thu, 13 Apr 2023 23:40:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id F3324C433A0; Thu, 13 Apr 2023 23:40:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1681429219; bh=y1tsCDiR9PB0QaZqwPHvaqN4LWmaz9Wyb/y9A7Tkf5Q=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=ZE0jiYJYP3cQM56F74mfHvqsS8Bkl2etzHgJ+mhyvwgEFuNYXzWCXxabfjm8Up+tu amXve31PQc2ZY+SKmEDoaDyRkR+MkD8lqU4+WTNTC6GXiOhUNTn+VPmtpNr+Y1UEaW 2yeipsDYoiTcpA10S2vkDWsubTSGQK3euLBKDn+6CVG4//QNhRCApbsLmaf/Dy7k2i swIRPhPMKGAJ2VXrcu6FdFwJEPP+Hf/WOjFyWXXDN1zBBhp2+ztgODOWDUPzICGTYl 4OPGgAMJSyqsejovCPxp5PrYhddY16ob788ybkaUKzBNEiAQH7RPcIOYxyaATYqqES y9QuQUC7AlEmw== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id D0646E52505; Thu, 13 Apr 2023 23:40:18 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to check return value of inc_valid_block_count() From: patchwork-bot+f2fs@kernel.org Message-Id: <168142921884.31957.17494916129948763212.git-patchwork-notify@kernel.org> Date: Thu, 13 Apr 2023 23:40:18 +0000 References: <20230405144536.930370-1-chao@kernel.org> In-Reply-To: <20230405144536.930370-1-chao@kernel.org> To: Chao Yu Cc: jaegeuk@kernel.org, daehojeong@google.com, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Wed, 5 Apr 2023 22:45:36 +0800 you wrote: > In __replace_atomic_write_block(), we missed to check return value > of inc_valid_block_count(), for extreme testcase that f2fs image is > run out of space, it may cause inconsistent status in between SIT > table and total valid block count. > > Cc: Daeho Jeong > Fixes: 3db1de0e582c ("f2fs: change the current atomic write way") > Signed-off-by: Chao Yu > > [...] Here is the summary with links: - [f2fs-dev] f2fs: fix to check return value of inc_valid_block_count() https://git.kernel.org/jaegeuk/f2fs/c/935fc6fa6466 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html