From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5C7EC7081A for ; Mon, 11 May 2026 01:42:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778463721; cv=none; b=tMuSRRUdFF3Lb6Pbct4bKDlGf9qN3aNUUPjb/T8ezfSo6T/Ykv+urcv77dbzITRXGEKSzeGrJ43qtSHqkMI89kOkY0Mj+qfK+R9RdoGR8g0OFqJXyDU/PfXW0Q0UedYnOOBklboTbLkhCso4XjT74dt7ZAANtEDDt6o8Q8YtsGA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778463721; c=relaxed/simple; bh=NhWA/tMq4xGZNefuWO6VqTj5/0PmjBtaHZj7SA7H4DU=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=B9mgHf+pBowJm/P6VOuIc6EVt3XLPQv4WVdIQsm4EmcFgOuWDEvIYZeBZ+8im9yDy8/TxPBxzdn0JBK2ja8Hzpo/itS9+lLhylPPu0OH3SXBzpTFFsvg1A46rOtdWCAGsKG4LDXjzPXAdg9sLnlh+UGGZ1oz3KNmXFlQYbpJHJ4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=JPgqVjhW; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="JPgqVjhW" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0366DC2BCB8; Mon, 11 May 2026 01:42:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778463721; bh=NhWA/tMq4xGZNefuWO6VqTj5/0PmjBtaHZj7SA7H4DU=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=JPgqVjhWEpTDzZENppPJjtZ1YPtOnuP83KywlJ3ezAFrxNIQlhJJfvcw00a/m+qTr 4h8JMBUVDuB3t0en1LK7R8s2yyb+j2/gMak5cHLa8eA8nGG4FpnC8gGaNqXy8RWwN6 AAlPsQ7PqW9lWBciEV6L1CvmPksyrxYj9vOswAEVCfwLGpkr+odnA5Cd+nSjOz0t9a /I0dZV+76drglHeHgALvoy4dCAc91IOybTfEkDgCbW641Qf655bXY9Kb64xmyL7gAU GLAvNfv5lQX+IyHm1/laAJtkObvATz51nI/ErZLlcmpaqnXxvcOEn+yTKcE4gIc0om lJcUC9y8NqYBQ== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 3FD8D3930039; Mon, 11 May 2026 01:41:09 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() From: patchwork-bot+f2fs@kernel.org Message-Id: <177846366788.1975880.13051192544864333031.git-patchwork-notify@kernel.org> Date: Mon, 11 May 2026 01:41:07 +0000 References: <20260427131050.1526593-2-monty_pavel@sina.com> In-Reply-To: <20260427131050.1526593-2-monty_pavel@sina.com> To: Yongpeng Yang Cc: chao@kernel.org, jaegeuk@kernel.org, yangyongpeng@xiaomi.com, stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 27 Apr 2026 21:10:51 +0800 you wrote: > From: Yongpeng Yang > > When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does > not reset the length of the largest extent to 0 and update the inode > folio. Since modifications to the extent tree are disallowed afterward, > the cached largest extent may become stale. This can trigger the > following error in xfstests generic/388: > > [...] Here is the summary with links: - [f2fs-dev,v2] f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node() https://git.kernel.org/jaegeuk/f2fs/c/5f8f16b73b46 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html