Files
linux/fs
Yongpeng Yang 1f70ddb28a f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()
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:

F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix

In the f2fs_drop_inode path, __destroy_extent_node() does not need to
guarantee that et->node_cnt is 0, because concurrency with writeback
is expected in this path, and writeback may update the extent cache.

This patch reverts commit ed78aeebef ("f2fs: fix node_cnt race between
extent node destroy and writeback"), and remove the unnecessary zero
check of et->node_cnt.

Fixes: ed78aeebef ("f2fs: fix node_cnt race between extent node destroy and writeback")
Cc: stable@vger.kernel.org
Reported-by: Chao Yu <chao@kernel.org>
Suggested-by: Chao Yu <chao@kernel.org>
Signed-off-by: Yongpeng Yang <yangyongpeng@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
2026-05-22 03:49:06 +00:00
..
2026-04-20 17:27:28 +02:00
2026-01-02 13:43:41 -05:00
2025-11-28 12:42:31 +01:00
2026-04-03 16:53:50 -04:00
2026-04-01 12:26:07 -07:00
2025-09-01 13:08:01 +02:00
2026-02-19 21:51:00 +09:00
2026-02-19 21:51:00 +09:00
2026-01-12 16:52:09 +01:00
2026-04-14 09:30:15 +02:00
2026-01-12 16:52:09 +01:00
2026-03-23 12:41:58 +01:00