mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	Nanzhe Zhao <nzzhao.sigma@gmail.com>,
	linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org, Barry Song <baohua@kernel.org>,
	Juan Yescas <jyescas@google.com>,
	Daeho Jeong <daehojeong@google.com>,
	Pengfei Li <lipengfei28@xiaomi.com>, Dev Jain <Dev.Jain@arm.com>,
	David Hildenbrand <David.Hildenbrand@arm.com>,
	linux-kernel@vger.kernel.org, Bo Zhang <zhangbo56@xiaomi.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	Nanzhe Zhao <nzzhao@126.com>, Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
	Ryan Roberts <Ryan.Roberts@arm.com>
Subject: Re: [PATCH v8 15/15] f2fs: make compressed files compatible with large folio
Date: Thu, 29 Oct 2026 15:12:32 +0800	[thread overview]
Message-ID: <54cbfb8a-c87e-4fea-9448-175706e22ac2@kernel.org> (raw)
In-Reply-To: <20261028154407.1601430-16-nzzhao.sigma@gmail.com>

On 10/28/26 23:44, Nanzhe Zhao wrote:
> From: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> 
> The compression flag is the hint indicates that the inode can be
> compressed, when the inode is using large folio, we expected it keeps
> using the large folio read/write paths and its data stays uncompressed
> on disk until the inode is evicted and re-read
> 
> Let f2fs_write_begin() skip the compression overwrite preparation for
> such inodes and remove the compressed-file gate in
> f2fs_read_data_large_folio() so the data is simply read/written as
> regular blocks.
> 
> For the same reason, reject F2FS_IOC_COMPRESS_FILE with -EOPNOTSUPP
> once the inode mapping is switched to large folios.
> 
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
>  Documentation/filesystems/f2fs.rst | 10 ++++++++
>  fs/f2fs/compress.c                 |  2 ++
>  fs/f2fs/data.c                     |  9 ++-----
>  fs/f2fs/file.c                     | 38 ++++++++++++++++++++++++++++++
>  4 files changed, 52 insertions(+), 7 deletions(-)
> 
> diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
> index 55798421f2c4..b79bb67ee78e 100644
> --- a/Documentation/filesystems/f2fs.rst
> +++ b/Documentation/filesystems/f2fs.rst
> @@ -942,6 +942,16 @@ Compression implementation
>    reserved via ioctl(F2FS_IOC_RESERVE_COMPRESS_BLOCKS) or the file size is
>    truncated to zero.
>  
> +- Compression and large folios are not effective at the same time on a file:
> +  a compressed inode does not use large folios, while an inode which is
> +  using large folios keeps its data uncompressed on disk.  If the compression
> +  flag is set on an inode that is already using large folios, the flag works
> +  as a hint until the inode is evicted: the inode keeps using the large folio
> +  read/write paths, f2fs_write_begin() skips the compression overwrite
> +  preparation, and ioctl(F2FS_IOC_COMPRESS_FILE) fails with -EOPNOTSUPP.
> +  Once the inode is evicted and read back, it uses order-0 folios again and
> +  compression is applied as usual.
> +
>  Compress metadata layout::
>  
>  				[Dnode Structure]
> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
> index 162bd8ef822a..721b01dd0d24 100644
> --- a/fs/f2fs/compress.c
> +++ b/fs/f2fs/compress.c
> @@ -78,6 +78,8 @@ bool f2fs_is_compressed_page(struct folio *folio)
>  		return false;
>  	if (folio_test_f2fs_nonpointer(folio))
>  		return false;
> +	if (f2fs_folio_has_ffs(folio))
> +		return false;
>  
>  	f2fs_bug_on(F2FS_F_SB(folio),
>  		*((u32 *)folio->private) != F2FS_COMPRESSED_PAGE_MAGIC);
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index cc3c9e51db9c..ab8f5b44d63a 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -3288,12 +3288,6 @@ static int f2fs_read_data_large_folio(struct inode *inode,
>  	int ret = 0;
>  	bool folio_in_bio = false;
>  
> -	if (f2fs_compressed_file(inode)) {
> -		if (folio)
> -			folio_unlock(folio);
> -		return -EOPNOTSUPP;
> -	}
> -
>  	map.m_seg_type = NO_CHECK_TYPE;
>  
>  	if (rac)
> @@ -5331,7 +5325,8 @@ static int f2fs_write_begin(const struct kiocb *iocb,
>  	}
>  
>  #ifdef CONFIG_F2FS_FS_COMPRESSION
> -	if (f2fs_compressed_file(inode)) {
> +	if (f2fs_compressed_file(inode) &&
> +	    !mapping_large_folio_support(inode->i_mapping)) {
>  		int ret;
>  		struct page *page;
>  
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 15bea642e986..cb7a9d4227f4 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -4907,6 +4907,7 @@ static int redirty_blocks(struct inode *inode, pgoff_t page_idx, int len)
>  	struct address_space *mapping = inode->i_mapping;
>  	struct folio *folio;
>  	pgoff_t redirty_idx = page_idx;
> +	pgoff_t end_idx = page_idx + len;
>  	int page_len = 0, ret = 0;
>  
>  	filemap_invalidate_lock_shared(mapping);
> @@ -4924,6 +4925,9 @@ static int redirty_blocks(struct inode *inode, pgoff_t page_idx, int len)
>  	} while (page_len < len);
>  
>  	while (redirty_idx < page_idx) {
> +		pgoff_t next_idx;
> +		size_t off, dlen;
> +
>  		folio = filemap_lock_folio(mapping, redirty_idx);
>  
>  		/* It will never fail, when folio has pinned above */
> @@ -4931,6 +4935,33 @@ static int redirty_blocks(struct inode *inode, pgoff_t page_idx, int len)
>  
>  		f2fs_folio_wait_writeback(folio, true, true);
>  
> +		/*
> +		 * Only this cluster is rewritten, while a large folio can
> +		 * cover more than one cluster, so mark the intersection of
> +		 * the folio and [redirty_idx, end_idx).
> +		 */
> +		next_idx = min_t(pgoff_t, folio_next_index(folio), end_idx);
> +		off = offset_in_folio(folio, (loff_t)redirty_idx << PAGE_SHIFT);
> +		dlen = (size_t)(next_idx - redirty_idx) << PAGE_SHIFT;
> +
> +		if (folio_test_large(folio)) {
> +			/*
> +			 * A compressed inode can keep using large folios, in
> +			 * which case the compression flag only works as a hint
> +			 * until the inode is evicted.  Update the subpage dirty
> +			 * bitmap as well, otherwise f2fs_write_cache_folios()
> +			 * finds no dirty range and skips the whole folio.
> +			 */
> +			if (!f2fs_ffs_find_or_alloc(folio)) {
> +				ret = -ENOMEM;
> +				folio_unlock(folio);
> +				folio_put_refs(folio, 2);
> +				redirty_idx = folio_next_index(folio);

Jaegeuk, Nanzhe,

I missed this potential UAF, please fix this.

diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 162b7f7aa6d4..3de67522beef 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -4941,16 +4941,14 @@ static int redirty_blocks(struct inode *inode, pgoff_t page_idx, int len)
                         */
                        if (!f2fs_ffs_find_or_alloc(folio)) {
                                ret = -ENOMEM;
-                               folio_unlock(folio);
-                               folio_put_refs(folio, 2);
-                               redirty_idx = folio_next_index(folio);
-                               continue;
+                               goto next;
                        }
                        f2fs_ffs_mark_subrange_dirty(folio, off, dlen);
                }

                folio_mark_dirty(folio);
                folio_set_f2fs_gcing(folio);
+next:
                redirty_idx = folio_next_index(folio);
                folio_unlock(folio);
                folio_put_refs(folio, 2);

Thanks,

> +				continue;
> +			}
> +			f2fs_ffs_mark_subrange_dirty(folio, off, dlen);
> +		}
> +
>  		folio_mark_dirty(folio);
>  		folio_set_f2fs_gcing(folio);
>  		redirty_idx = folio_next_index(folio);
> @@ -5037,6 +5068,13 @@ static int f2fs_ioc_compress_file(struct file *filp)
>  	if (!(filp->f_mode & FMODE_WRITE))
>  		return -EBADF;
>  
> +	/*
> +	 * The mapping is already using large folios, where the data is kept
> +	 * uncompressed, so refuse to start compressing the file.
> +	 */
> +	if (mapping_large_folio_support(inode->i_mapping))
> +		return -EOPNOTSUPP;
> +
>  	f2fs_balance_fs(sbi, true);
>  
>  	ret = mnt_want_write_file(filp);


  parent reply	other threads:[~2026-10-29  7:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 15:43 [PATCH v8 00/15] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-10-28 15:43 ` [PATCH v8 01/15] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-10-29  1:30   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 02/15] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-10-29  1:31   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 03/15] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-10-29  1:31   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 04/15] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-10-29  1:31   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 05/15] f2fs: support large folio writeback Nanzhe Zhao
2026-10-29  1:32   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 06/15] f2fs: account large folio dirty data at block granularity Nanzhe Zhao
2026-10-29  1:32   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 07/15] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-10-29  1:32   ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 08/15] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-10-29  1:32   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 09/15] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-10-29  1:33   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 10/15] f2fs: support partial uptodate " Nanzhe Zhao
2026-10-29  1:33   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 11/15] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-10-29  1:34   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 12/15] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-10-29  1:34   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 13/15] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-10-29  1:35   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 14/15] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-10-29  1:36   ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 15/15] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-10-29  1:36   ` Chao Yu
2026-10-29  7:12   ` Chao Yu [this message]
2026-10-29 15:17     ` [f2fs-dev] " Jaegeuk Kim
2026-10-28 17:34 ` [f2fs-dev] [PATCH v8 00/15] f2fs: support & optimize large folios for writable files Jaegeuk Kim

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=54cbfb8a-c87e-4fea-9448-175706e22ac2@kernel.org \
    --to=chao@kernel.org \
    --cc=David.Hildenbrand@arm.com \
    --cc=Dev.Jain@arm.com \
    --cc=Ryan.Roberts@arm.com \
    --cc=baohua@kernel.org \
    --cc=daehojeong@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=jyescas@google.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipengfei28@xiaomi.com \
    --cc=nzzhao.sigma@gmail.com \
    --cc=nzzhao@126.com \
    --cc=zhangbo56@xiaomi.com \
    --cc=zhaonanzhe@xiaomi.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

all inboxes | Powered by JetHome®