On Mon, Sep 16, 2024 at 07:19:21PM +0530, Kanchan Joshi wrote:
> > Maybe part of the problem is that the API is very confusing. A smal
> > part of that is of course that the existing temperature hints already
> > have some issues, but this seems to be taking them make it significantly
> > worse.
>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Mon, 9 Sep 2024 15:19:40 -0700 you wrote:
> From: Daeho Jeong
>
> Since we don't have any GC on device side for zoned devices, need more
> aggressive BG GC. So, tune the parameters for that.
>
> Signed-off-by: Daeho
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Tue, 10 Sep 2024 11:07:13 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> [ cut here ]
> WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180
> kernel/rcu/sync.c:1
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Sun, 15 Sep 2024 03:22:51 + you wrote:
> This patch allows f2fs to submit bios of in-place writes on pinned file.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/sysfs.c | 3 ++-
> 1 file changed, 2 insertions(+), 1
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Tue, 10 Sep 2024 09:16:19 +0800 you wrote:
> f2fs: fix to don't panic system for no free segment fault injection
>
> syzbot reports a f2fs bug as below:
>
> F2FS-fs (loop0): inject no free segment in get_new_segment of
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Wed, 4 Sep 2024 08:33:06 -0700 you wrote:
> From: Daeho Jeong
>
> Keep atomic file clean while updating and make it dirtied during commit
> in order to avoid unnecessary and excessive inode updates in the previous
> fi
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Fri, 6 Sep 2024 14:27:24 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> kernel BUG at fs/f2fs/inode.c:896!
> RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896
> Call Trace:
> evict+0x532/0x950 fs
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Thu, 12 Sep 2024 09:59:58 -0700 you wrote:
> From: Daeho Jeong
>
> We need to migrate data blocks even though it is full to secure space
> for zoned device file pinning.
>
> Signed-off-by: Daeho Jeong
> Fixes: 9703d69
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Patch: [f2fs-dev,v2] f2fs: forcibly migrate to secure space for zoned device
file pinning
Submitter: Daeho Jeong
Committer: Jaegeuk Kim
Patchwork: https://patchwork.kernel.org/projec
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Thu, 05 Sep 2024 14:24:33 +0900 you wrote:
> This patch addresses the problem that when using LFS mode, unused blocks
> may occur in f2fs_map_blocks() during block allocation for dio writes.
>
> If a new section is alloc
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Wed, 4 Sep 2024 11:20:47 +0800 you wrote:
> Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(),
> f2fs_move_file_range(), and f2fs_defragment_range() missed to
> check atomic_write status, which may cause potential
On Sat, Sep 14, 2024 at 8:24 PM Jaegeuk Kim via Linux-f2fs-devel
wrote:
>
> This patch allows f2fs to submit bios of in-place writes on pinned file.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/sysfs.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/sysfs.c b
From: Daeho Jeong
We can add a device aliasing file which can map the whole device with an
extent, not using node blocks. This mapped area should be pinned and
normally used for read-only usages. After finished using it, we can
deallocate the whole area and return it back to use it for other file
From: Daeho Jeong
Current description confuses users like they can add addtional devices
with one -c option using commas(,) at the same time.
Signed-off-by: Daeho Jeong
---
mkfs/f2fs_format_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mkfs/f2fs_format_main.c b/mkf
On Mon, Sep 16, 2024 at 10:10 AM Jaegeuk Kim wrote:
>
> On 09/16, Daeho Jeong wrote:
> > On Fri, Sep 13, 2024 at 3:27 PM Jaegeuk Kim wrote:
> > >
> > > On 09/13, Daeho Jeong wrote:
> > > > From: Daeho Jeong
> > > >
> > > > We can add a device aliasing file which can map the whole device with an
On 09/16, Daeho Jeong wrote:
> On Fri, Sep 13, 2024 at 3:27 PM Jaegeuk Kim wrote:
> >
> > On 09/13, Daeho Jeong wrote:
> > > From: Daeho Jeong
> > >
> > > We can add a device aliasing file which can map the whole device with an
> > > extent, not using node blocks. This mapped area should be pinne
On Fri, Sep 13, 2024 at 3:27 PM Jaegeuk Kim wrote:
>
> On 09/13, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > We can add a device aliasing file which can map the whole device with an
> > extent, not using node blocks. This mapped area should be pinned and
> > normally used for read-only usage
Hello,
syzbot found the following issue on:
HEAD commit:98f7e32f20d2 Linux 6.11
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13a5e27798
kernel config: https://syzkaller.appspot.com/x/.config?x=c78874575ba70f27
dashboard link: https://syzkaller.appspo
On 9/13/2024 1:36 PM, Christoph Hellwig wrote:
> On Thu, Sep 12, 2024 at 10:01:00PM +0530, Kanchan Joshi wrote:
>> Please see the response in patch #1. My worries were:
>> (a) adding a new field and propagating it across the stack will cause
>> code duplication.
>> (b) to add a new field we need to
Hello f2fs maintainers/developers,
This is a 31-day syzbot report for the f2fs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/f2fs
During the period, 1 new issues were detected and 0 were fixed.
In total, 8 issues are still open and 41 have be
20 matches
Mail list logo
