From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794046501; b=3TfWHwG2l0CfzOgPHuSads2zSeyT6NDeVhhhe2u5VWKQSjGsv+H74aiguCQcR/mHPVuE 39QBfQdn6Ku59hbOk/Aum4IuCstfxDsoJjHR6DqfL4sgqKAFqk80AAQhGGLPoaPinxN0k vXeFOIs3wqmCZPJVadUA2rbpeSo6lb+XL2xUD1pJKw2OhgUMvwpgIX6qlEW45vXpQ1yUz xsT8fRyzNOw8v7EIJgrYR7jEo9CCNyNNVTSS8xIXPXY4bIfmp73HTv15WR/9KCToU66vw sk023fzU7dZIqR89ZeRThZdip9fbriqtL8EFZxLGDMNNczd65PxV8mXLYF/JBabVayQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794046501; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=3YcsBXsdhpmoXJ2jJK1YS3XZTC3ykpd+p2duB+EBVqw=; b=j50i2zYlFuhe45rTz5RQSC1ghr5QZ/RMR6KvE7RCp7xk0uxZVJL7DDacnjKConSv2gd8 XgoPUT77qcILVuYT+5FzdoWkERdS3zqWDxy2bO8bhte1C6WqHfI8nGDpnGmYKjJvSs+0Z ptjVdsoRHoKKDLFx2fs3knwq4nPkEXbwxV0lEIYu/Mvb3yzSXwsty/u1KZaDGr8FbdItJ uRxs6fq/4dnZjMNlx9O82UbpOpRPZXFJM1Dm32eHOaSQPDC9ash3RPmndxtO61gruJ4GC yP0kWIEnkQrHVS6Mtd7rEBJs1kuXql8j0bQz5T9peD7bbA8m64V9At1ivnEQj0ZtHSw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=iDvrRjYS; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6823D606A32D for ; Sat, 7 Nov 2026 10:15:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=iDvrRjYS Received: by smtp.kernel.org (Postfix) with ESMTPSA id B63FD1F0089F; Sat, 7 Nov 2026 10:15:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794046501; bh=3YcsBXsdhpmoXJ2jJK1YS3XZTC3ykpd+p2duB+EBVqw=; h=From:To:Cc:Subject:Date; b=iDvrRjYSzYzTZB5DWW89ecCOANMr4idlmpqZUcPpaiIVI6uRJi8fjBqAVia17BwlI HvDlv3myzoHzacdTZBUfXHxnBWjIxeFmpAJyiekeEVubjbaYRy3DZLJ5nft+VkKMpS Iiu/XzdlE9nqpZfURr8YB/aY+FqQMjqbIoq4GbBHtiGxhmNsET36wvVP/ho6xfjcgU uBMkQHSdoVv7E/gkLCyDwsXIN5uPQ2igNuT7zlokGope+UgHG97Ndxci0KYY6TI1ZB RS2eL4OihhXIxXFDuccf80mT2Bn87XfQGNJ50jbJTDGe5gZlnvYbE0I9X5UrdydibF lLEG01bVbZpjg== From: Sasha Levin To: chao@kernel.org, jaegeuk@kernel.org Cc: stable@vger.kernel.org Subject: FAILED: patch "[PATCH] f2fs: fix to fetch ino via ino_of_node() under cache lock" failed to apply to 6.18-stable tree Date: Sat, 7 Nov 2026 05:14:58 -0500 Message-ID: <20261107051458-failed-6.18-cd6d8b189139@kernel.org> X-Mailer: git-send-email 2.53.0 X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The patch below does not apply to the 6.18-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.18.y git checkout FETCH_HEAD git cherry-pick -x cd6d8b1891395b681f2060916a4b83880b765698 # git commit -s git send-email --to '' --in-reply-to '20261107051458-failed-6.18-cd6d8b189139@kernel.org' --subject-prefix 'PATCH 6.18.y' 'HEAD^..' Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From cd6d8b1891395b681f2060916a4b83880b765698 Mon Sep 17 00:00:00 2001 From: Chao Yu Date: Mon, 26 Oct 2026 08:23:49 +0800 Subject: [PATCH] f2fs: fix to fetch ino via ino_of_node() under cache lock In f2fs_writeback_node_caches(), it's better to fetch ino via ino_of_node() under cache lock, otherwise, node cache content may become stale after cache is unlocked due to racing w/ truncation. Commit 493b9dc8b52c ("f2fs: cache: use node cache") fixes similar issue in f2fs_flush_inline_data() introduced in commit 34c061ad85a2 ("f2fs: Avoid double lock for cp_rwsem during checkpoint"). Cc: stable@kernel.org Fixes: 2049d4fcb057 ("f2fs: avoid multiple node page writes due to inline_data") Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim --- fs/f2fs/node.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c index 424e95ca58789..44f94000d452c 100644 --- a/fs/f2fs/node.c +++ b/fs/f2fs/node.c @@ -2195,9 +2195,11 @@ int f2fs_writeback_node_caches(struct f2fs_sb_info *sbi, long nr_to_write, /* flush inline_data */ if (f2fs_cache_test_inline(entry)) { + nid_t ino = ino_of_node(sbi, entry); + f2fs_cache_clear_inline(entry); f2fs_unlock_cache(entry); - flush_inline_data(sbi, ino_of_node(sbi, entry)); + flush_inline_data(sbi, ino); goto lock_node; } -- 2.53.0