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 16C3AC77B61 for ; Mon, 24 Apr 2023 18:10:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232107AbjDXSKX (ORCPT ); Mon, 24 Apr 2023 14:10:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231411AbjDXSKV (ORCPT ); Mon, 24 Apr 2023 14:10:21 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B16E6729E for ; Mon, 24 Apr 2023 11:10: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 4732D627FD for ; Mon, 24 Apr 2023 18:10:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 9694BC4339C; Mon, 24 Apr 2023 18:10:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1682359819; bh=K9tNHJzMGBqsZycX/xsTz73dgSOGSW5hOL6e8j1XH9A=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=gePJThZsgqSjZHL+qhbsoACUtLJUrJVkMxJq8Z1ZIMrhiNxJVFeTyuiPAWYnBq4XG ixU3Zcw91ucVX/T4WUTmQO4jKuHFXChTbuxEySoAf3VcFHfe7Wrf8halgzNogf1pUW F1QveXsnu5YLomXK2mKPpU757eJPXC5nTXVQ4+YsCTdrvQc36/n0xGXYfFmmM5CUJW DwMMZNQMcNmv3Rjqlk+wkHumwQKXuSxuGsEz6saDr1MKxMcBu8QjItJLWuw+0kH9sU 5SJJ6BjvlXXtNqM8D2K09iUuQUKUzmEQUEGDS3GRgOFWt6DOVAJAKq4QvD167c//Ya QQayw6qmtpquA== 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 73FA0E4508E; Mon, 24 Apr 2023 18:10:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: use cow inode data when updating atomic write From: patchwork-bot+f2fs@kernel.org Message-Id: <168235981947.17900.2626518679840712384.git-patchwork-notify@kernel.org> Date: Mon, 24 Apr 2023 18:10:19 +0000 References: <20230424154348.22885-1-daeho43@gmail.com> In-Reply-To: <20230424154348.22885-1-daeho43@gmail.com> To: Daeho Jeong Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com, daehojeong@google.com 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 Mon, 24 Apr 2023 08:43:48 -0700 you wrote: > From: Daeho Jeong > > Need to use cow inode data content instead of the one in the original > inode, when we try to write the already updated atomic write files. > > Fixes: 3db1de0e582c ("f2fs: change the current atomic write way") > Signed-off-by: Daeho Jeong > > [...] Here is the summary with links: - [f2fs-dev] f2fs: use cow inode data when updating atomic write https://git.kernel.org/jaegeuk/f2fs/c/591fc34e1f98 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html