Hello: This series was applied to jaegeuk/f2fs.git (dev) by Eric Biggers <[email protected]>:
On Mon, 2 Feb 2026 07:06:30 +0100 you wrote: > Issuing more reads on errors is not a good idea, especially when the > most common error here is -ENOMEM. > > Signed-off-by: Christoph Hellwig <[email protected]> > --- > fs/verity/pagecache.c | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) Here is the summary with links: - [f2fs-dev,01/11] fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio https://git.kernel.org/jaegeuk/f2fs/c/23eec9fd64b2 - [f2fs-dev,02/11] readahead: push invalidate_lock out of page_cache_ra_unbounded (no matching commit) - [f2fs-dev,03/11] ext4: move ->read_folio and ->readahead to readahead.c (no matching commit) - [f2fs-dev,04/11] fsverity: kick off hash readahead at data I/O submission time (no matching commit) - [f2fs-dev,05/11] fsverity: deconstify the inode pointer in struct fsverity_info https://git.kernel.org/jaegeuk/f2fs/c/7e36e044958d - [f2fs-dev,06/11] fsverity: push out fsverity_info lookup (no matching commit) - [f2fs-dev,07/11] fs: consolidate fsverity_info lookup in buffer.c https://git.kernel.org/jaegeuk/f2fs/c/f6ae956dfb34 - [f2fs-dev,08/11] ext4: consolidate fsverity_info lookup (no matching commit) - [f2fs-dev,09/11] f2fs: consolidate fsverity_info lookup (no matching commit) - [f2fs-dev,10/11] btrfs: consolidate fsverity_info lookup https://git.kernel.org/jaegeuk/f2fs/c/b0160e4501bb - [f2fs-dev,11/11] fsverity: use a hashtable to find the fsverity_info (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
