From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/6] f2fs: fix to return correct error number in f2fs_sync_node_pages()
Date: Thu, 08 May 2025 16:30:30 +0000 [thread overview]
Message-ID: <174672183025.2971823.13421016836031371111.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250508051520.4169795-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 8 May 2025 07:14:27 +0200 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> If __write_node_folio() failed, it will return AOP_WRITEPAGE_ACTIVATE,
> the incorrect return value may be passed to userspace in below path,
> fix it.
>
> - sync_filesystem
> - sync_fs
> - f2fs_issue_checkpoint
> - block_operations
> - f2fs_sync_node_pages
> - __write_node_folio
> : return AOP_WRITEPAGE_ACTIVATE
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/6] f2fs: fix to return correct error number in f2fs_sync_node_pages()
https://git.kernel.org/jaegeuk/f2fs/c/43ba56a043b1
- [f2fs-dev,2/6] f2fs: return bool from __f2fs_write_meta_folio
https://git.kernel.org/jaegeuk/f2fs/c/39122e454419
- [f2fs-dev,3/6] f2fs: remove wbc->for_reclaim handling
https://git.kernel.org/jaegeuk/f2fs/c/402dd9f02ce4
- [f2fs-dev,4/6] f2fs: always unlock the page in f2fs_write_single_data_page
https://git.kernel.org/jaegeuk/f2fs/c/84c5d16711a3
- [f2fs-dev,5/6] f2fs: simplify return value handling in f2fs_fsync_node_pages
https://git.kernel.org/jaegeuk/f2fs/c/0638f28b3062
- [f2fs-dev,6/6] f2fs: return bool from __write_node_folio
https://git.kernel.org/jaegeuk/f2fs/c/80f31d2a7e5f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-05-08 16:29 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 ` patchwork-bot+f2fs [this message]
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
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=174672183025.2971823.13421016836031371111.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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