[f2fs-dev] [PATCH] f2fs: drop non uptodata page during GC

From: Yunlei He GC move fbe data block will add some non uptodate page, we'd better release it at the end. Signed-off-by: Yunlei He Signed-off-by: Yongpeng Yang --- fs/f2fs/gc.c | 5 + 1 file changed, 5 insertions(+) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c index 8abf521530ff..09b65e6ea8

Re: [f2fs-dev] [PATCH] vfs: remove the excl argument from the ->create() inode_operation

On Fri, 07 Nov 2025, Jeff Layton wrote: > On Thu, 2025-11-06 at 07:07 -0500, Jeff Layton wrote: > > On Thu, 2025-11-06 at 08:23 +1100, NeilBrown wrote: > > > On Thu, 06 Nov 2025, Jeff Layton wrote: > > > > Since ce8644fcadc5 ("lookup_open(): expand the call of vfs_create()"), > > > > the "excl" arg

Re: [f2fs-dev] [syzbot] [iomap?] kernel BUG in folio_end_read (2)

On 2025-11-06, John Ogness wrote: >> I think that we should do the following: >> >> diff --git a/kernel/printk/printk_ringbuffer.c >> b/kernel/printk/printk_ringbuffer.c >> index 839f504db6d3..78e02711872e 100644 >> --- a/kernel/printk/printk_ringbuffer.c >> +++ b/kernel/printk/printk_ringbuffer.

Re: [f2fs-dev] [syzbot] [iomap?] kernel BUG in folio_end_read (2)

On 2025-11-06, Petr Mladek wrote: >> diff --git a/kernel/printk/printk_ringbuffer.c >> b/kernel/printk/printk_ringbuffer.c >> index 839f504db6d30..8499ee642c31d 100644 >> --- a/kernel/printk/printk_ringbuffer.c >> +++ b/kernel/printk/printk_ringbuffer.c >> @@ -390,6 +390,17 @@ static unsigned int

Re: [f2fs-dev] [PATCH] vfs: remove the excl argument from the ->create() inode_operation

On Thu, 2025-11-06 at 07:07 -0500, Jeff Layton wrote: > On Thu, 2025-11-06 at 08:23 +1100, NeilBrown wrote: > > On Thu, 06 Nov 2025, Jeff Layton wrote: > > > Since ce8644fcadc5 ("lookup_open(): expand the call of vfs_create()"), > > > the "excl" argument to the ->create() inode_operation is always

Re: [f2fs-dev] [syzbot] [iomap?] kernel BUG in folio_end_read (2)

On Thu 2025-11-06 12:42:21, John Ogness wrote: > On 2025-11-05, John Ogness wrote: > >> Another question is whether this is the only problem caused the patch. > > > > This comparison is quite special. It caught my attention while combing > > through the code. > > The reason that this comparison i

Re: [f2fs-dev] [PATCH] vfs: remove the excl argument from the ->create() inode_operation

On Thu, 2025-11-06 at 08:23 +1100, NeilBrown wrote: > On Thu, 06 Nov 2025, Jeff Layton wrote: > > Since ce8644fcadc5 ("lookup_open(): expand the call of vfs_create()"), > > the "excl" argument to the ->create() inode_operation is always set to > > true. Remove it, and fix up all of the create imple

Re: [f2fs-dev] [syzbot] [iomap?] kernel BUG in folio_end_read (2)

On 2025-11-05, John Ogness wrote: >> Another question is whether this is the only problem caused the patch. > > This comparison is quite special. It caught my attention while combing > through the code. The reason that this comparison is special is because it is the only one that does not take wr

[f2fs-dev] [PATCH 1/2] f2fs: rename and refactor sbi->unusable_blocks_per_sec

From: Yongpeng Yang sbi->unusable_blocks_per_sec is used only within CONFIG_BLK_DEV_ZONED sections, except for CAP_BLKS_PER_SEC and CAP_SEGS_PER_SEC. This patch renames unusable_blocks_per_sec to unusable_blocks_per_blkz and ensures that unusable_blocks_per_blkz is properly enclosed within the CO

[f2fs-dev] [PATCH 2/2] f2fs: fix handling of block devices with max_open_zones == 0

From: Yongpeng Yang When the block device reports max_open_zones == 0, sbi->max_open_zones is initialized to UINT_MAX. In such cases, F2FS can still be mounted successfully (as tested under qemu). However, for SSDs, a device reporting max_open_zones == 0 should not be mountable, while for SMR HDD