mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Wenjie Qi <qwjhust@gmail.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, qiwenjie@xiaomi.com
Subject: Re: [PATCH] f2fs: validate compress cache inode only when enabled
Date: Thu, 21 May 2026 16:37:51 +0800	[thread overview]
Message-ID: <a36697b3-60d5-4677-87b3-52a6f954fa39@kernel.org> (raw)
In-Reply-To: <20260521031618.1734199-1-qiwenjie@xiaomi.com>

On 5/21/26 11:16, Wenjie Qi wrote:
> F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode
> number for the compressed page cache inode. That inode only exists when
> the compress_cache mount option is enabled.
> 
> When compress_cache is disabled, max_nid is outside the valid inode
> range. A corrupted directory entry that points to ino == max_nid should
> therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino()
> currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally,
> so f2fs_iget() bypasses do_read_inode() and its nid range check, and
> instantiates a fake internal inode instead.
> 
> Gate the compressed cache inode case on COMPRESS_CACHE, matching
> f2fs_init_compress_inode(). With compress_cache disabled, ino ==
> max_nid now follows the normal inode path and is rejected as an
> out-of-range nid.
> 

Cc: stable@kernel.org

> Fixes: 6ce19aff0b8c ("f2fs: compress: add compress_inode to cache compressed blocks")
> Signed-off-by: Wenjie Qi <qiwenjie@xiaomi.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

      reply	other threads:[~2026-05-21  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  3:16 Wenjie Qi
2026-05-21  8:37 ` Chao Yu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a36697b3-60d5-4677-87b3-52a6f954fa39@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiwenjie@xiaomi.com \
    --cc=qwjhust@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome