The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] f2fs: remove wbc->for_reclaim handling
Date: Thu, 8 May 2025 17:46:24 +0800	[thread overview]
Message-ID: <bea92b8e-c20e-4dcf-91b5-4af4f71b00ef@kernel.org> (raw)
In-Reply-To: <20250508051520.4169795-4-hch@lst.de>

On 5/8/25 13:14, Christoph Hellwig wrote:
> Since commits 7ff0104a8052 ("f2fs: Remove f2fs_write_node_page()") and
> 3b47398d9861 ("f2fs: Remove f2fs_write_meta_page()'), f2fs can't be
> called from reclaim context any more.  Remove all code keyed of the
> wbc->for_rename flag, which is now only set for writing out swap or

s/for_rename/for_reclaim

I guess Jaegeuk can fix this during merge.

> shmem pages inside the swap code, but never passed to file systems.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

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

Thanks,


  reply	other threads:[~2025-05-08  9:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  5:14 cleanup AOP_WRITEPAGE_ACTIVATE use in f2fs v2 Christoph Hellwig
2025-05-08  5:14 ` [PATCH 1/6] f2fs: fix to return correct error number in f2fs_sync_node_pages() Christoph Hellwig
2025-05-08 16:30   ` [f2fs-dev] " patchwork-bot+f2fs
2025-05-08  5:14 ` [PATCH 2/6] f2fs: return bool from __f2fs_write_meta_folio Christoph Hellwig
2025-05-08  5:14 ` [PATCH 3/6] f2fs: remove wbc->for_reclaim handling Christoph Hellwig
2025-05-08  9:46   ` Chao Yu [this message]
2025-05-08  5:14 ` [PATCH 4/6] f2fs: always unlock the page in f2fs_write_single_data_page Christoph Hellwig
2025-05-08  9:48   ` Chao Yu
2025-05-08  5:14 ` [PATCH 5/6] f2fs: simplify return value handling in f2fs_fsync_node_pages Christoph Hellwig
2025-05-08  9:53   ` Chao Yu
2025-05-08  5:14 ` [PATCH 6/6] f2fs: return bool from __write_node_folio Christoph Hellwig

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=bea92b8e-c20e-4dcf-91b5-4af4f71b00ef@kernel.org \
    --to=chao@kernel.org \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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