[f2fs-dev] [PATCH -next] f2fs: fix wrong dirty page count when race between mmap and fallocate.

This is a BUG_ON issue as follows when running xfstest-generic-503: WARNING: CPU: 21 PID: 1385 at fs/f2fs/inode.c:762 f2fs_evict_inode+0x847/0xaa0 Modules linked in: CPU: 21 PID: 1385 Comm: umount Not tainted 5.19.0-rc5+ #73 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-4.fc34

Re: [f2fs-dev] [PATCH v3 5/5] fscrypt: remove fscrypt_set_test_dummy_encryption()

On Fri, May 13, 2022 at 04:16:05PM -0700, Eric Biggers wrote: > From: Eric Biggers > > Now that all its callers have been converted to > fscrypt_parse_test_dummy_encryption() and fscrypt_add_test_dummy_key() > instead, fscrypt_set_test_dummy_encryption() can be removed. > > Signed-off-by: Eric B

[f2fs-dev] [PATCH v2 1/2] fscrypt: stop using PG_error to track error status

From: Eric Biggers As a step towards freeing the PG_error flag for other uses, change ext4 and f2fs to stop using PG_error to track decryption errors. Instead, if a decryption error occurs, just mark the whole bio as failed. The coarser granularity isn't really a problem since it isn't any wors

[f2fs-dev] [PATCH v2 0/2] ext4, f2fs: stop using PG_error for fscrypt and fsverity

This series changes ext4 and f2fs to stop using PG_error to track decryption and verity errors. This is a step towards freeing up PG_error for other uses, as discussed at https://lore.kernel.org/linux-fsdevel/yn10iz1mjx1mu...@casper.infradead.org Note: due to the interdependencies with fs/crypto/

[f2fs-dev] [PATCH v2 2/2] fsverity: stop using PG_error to track error status

From: Eric Biggers As a step towards freeing the PG_error flag for other uses, change ext4 and f2fs to stop using PG_error to track verity errors. Instead, if a verity error occurs, just mark the whole bio as failed. The coarser granularity isn't really a problem since it isn't any worse than w

Re: [f2fs-dev] [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes

On Sat, Jul 30, 2022 at 08:08:26PM -0700, Jaegeuk Kim wrote: > On 07/25, Eric Biggers wrote: > > On Sat, Jul 23, 2022 at 07:01:59PM -0700, Jaegeuk Kim wrote: > > > On 07/22, Eric Biggers wrote: > > > > From: Eric Biggers > > > > > > > > Currently, if an f2fs filesystem is mounted with the mode=lf

[f2fs-dev] [PATCH] mkfs.f2fs: catch total_zones=0 instead of crashing

From: Eric Biggers Cleanly report an error instead of dividing by 0 (causing a floating point exception) in the following case: truncate -s 16M img && mkfs.f2fs img Note that this is a minimal fix; it appears that overly-small images still cause various integer overflows in f2fs_prepare