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 9648AEB64DA for ; Fri, 30 Jun 2023 23:40:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232367AbjF3Xkl (ORCPT ); Fri, 30 Jun 2023 19:40:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45364 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232095AbjF3Xk1 (ORCPT ); Fri, 30 Jun 2023 19:40:27 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A93E62D50 for ; Fri, 30 Jun 2023 16:40:24 -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 4606861838 for ; Fri, 30 Jun 2023 23:40:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 94705C433CB; Fri, 30 Jun 2023 23:40:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1688168423; bh=W0fQjv0ep+Qe26cn8QnkVVT2df49/M4iytcJ2vTwNJU=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=mzkw6nJ+d4pb2/B1TPMpQ6h4tzqE7rbdjUM8YmEMOCnT01IeUxM4Hzk4mHAazSVGF cDKMjj3DMu2lQKK+D2VOQt/quQidghPReFENu3uCnym7rzvE1Iaf/6aSwLbMvjjIsv DZ56aHE7KwZ+UFHgSvkRcReVomyqN60vPoJcUNIAgKLUSwWNEZSF+cckY85vzdJKJN yIMYAEFWK341koYhVON+sG5eHw2xXqd4KB3LV8xLOnbCGxxjupiW1khvAXfUV456pm LR+d6XSTP28wDd9FOWquCxf3RNIL5MG5lUn+zTRoZPdz6CWmKomdx7kSahLug/rCcj z/UEHbDpu7p9w== 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 61669C395D8; Fri, 30 Jun 2023 23:40:23 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: fix error path handling in truncate_dnode() From: patchwork-bot+f2fs@kernel.org Message-Id: <168816842339.31915.12136963256323192911.git-patchwork-notify@kernel.org> Date: Fri, 30 Jun 2023 23:40:23 +0000 References: <20230629014102.3057853-1-chao@kernel.org> In-Reply-To: <20230629014102.3057853-1-chao@kernel.org> To: Chao Yu Cc: jaegeuk@kernel.org, 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 Thu, 29 Jun 2023 09:41:02 +0800 you wrote: > If truncate_node() fails in truncate_dnode(), it missed to call > f2fs_put_page(), fix it. > > Fixes: 7735730d39d7 ("f2fs: fix to propagate error from __get_meta_page()") > Signed-off-by: Chao Yu > --- > fs/f2fs/node.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) Here is the summary with links: - [f2fs-dev] f2fs: fix error path handling in truncate_dnode() https://git.kernel.org/jaegeuk/f2fs/c/0135c482fa97 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html