public inbox for linux-fscrypt@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fscrypt@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] f2fs: remove unreachable code in f2fs_encrypt_one_page()
Date: Mon, 23 Feb 2026 14:22:45 +0100	[thread overview]
Message-ID: <94f41e2a-53c1-4b7c-8f6c-4553ae729608@kernel.org> (raw)
In-Reply-To: <20260221201316.22025-1-ebiggers@kernel.org>

On 2/21/26 21:13, Eric Biggers wrote:
> Since commit 52e7e0d88933 ("fscrypt: Switch to sync_skcipher and
> on-stack requests") eliminated the dynamic allocation of crypto
> requests, the only remaining dynamic memory allocation done by
> fscrypt_encrypt_pagecache_blocks() is the bounce page allocation.
> 
> The bounce page is allocated from a mempool.  Mempool allocations with
> GFP_NOFS never fail.  Therefore, fscrypt_encrypt_pagecache_blocks() can
> no longer return -ENOMEM when passed GFP_NOFS.
> 
> Remove the now-unreachable code from f2fs_encrypt_one_page().
> 
> Suggested-by: Vlastimil Babka <vbabka@suse.cz>
> Link: https://lore.kernel.org/all/d9dc2ee1-283d-4467-ad36-a6a4aa557589@suse.cz/
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>

Acked-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>

Thanks!

> ---
>  fs/f2fs/data.c | 14 ++------------
>  1 file changed, 2 insertions(+), 12 deletions(-)
> 
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 338df7a2aea6..400f0400e13d 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -2785,33 +2785,23 @@ static void f2fs_readahead(struct readahead_control *rac)
>  int f2fs_encrypt_one_page(struct f2fs_io_info *fio)
>  {
>  	struct inode *inode = fio_inode(fio);
>  	struct folio *mfolio;
>  	struct page *page;
> -	gfp_t gfp_flags = GFP_NOFS;
>  
>  	if (!f2fs_encrypted_file(inode))
>  		return 0;
>  
>  	page = fio->compressed_page ? fio->compressed_page : fio->page;
>  
>  	if (fscrypt_inode_uses_inline_crypto(inode))
>  		return 0;
>  
> -retry_encrypt:
>  	fio->encrypted_page = fscrypt_encrypt_pagecache_blocks(page_folio(page),
> -					PAGE_SIZE, 0, gfp_flags);
> -	if (IS_ERR(fio->encrypted_page)) {
> -		/* flush pending IOs and wait for a while in the ENOMEM case */
> -		if (PTR_ERR(fio->encrypted_page) == -ENOMEM) {
> -			f2fs_flush_merged_writes(fio->sbi);
> -			memalloc_retry_wait(GFP_NOFS);
> -			gfp_flags |= __GFP_NOFAIL;
> -			goto retry_encrypt;
> -		}
> +					PAGE_SIZE, 0, GFP_NOFS);
> +	if (IS_ERR(fio->encrypted_page))
>  		return PTR_ERR(fio->encrypted_page);
> -	}
>  
>  	mfolio = filemap_lock_folio(META_MAPPING(fio->sbi), fio->old_blkaddr);
>  	if (!IS_ERR(mfolio)) {
>  		if (folio_test_uptodate(mfolio))
>  			memcpy(folio_address(mfolio),
> 
> base-commit: 8934827db5403eae57d4537114a9ff88b0a8460f


  parent reply	other threads:[~2026-02-23 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-21 20:13 [PATCH] f2fs: remove unreachable code in f2fs_encrypt_one_page() Eric Biggers
2026-02-23 13:13 ` Christoph Hellwig
2026-02-23 13:22 ` Vlastimil Babka (SUSE) [this message]
2026-03-04  7:53 ` Chao Yu

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=94f41e2a-53c1-4b7c-8f6c-4553ae729608@kernel.org \
    --to=vbabka@kernel.org \
    --cc=chao@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=hch@infradead.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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