some user behaviors requested filesystem operations, which
will cause filesystem not idle.
Meanwhile adjust f2fs_update_time(REQ_TIME) of
f2fs_ioc_defragment to successful case.
Signed-off-by: Zhiguo Niu
---
fs/f2fs/file.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff
On 2024/3/13 4:49, Daeho Jeong wrote:
From: Daeho Jeong
In a case writing without fallocate(), we can't guarantee it's allocated
in the conventional area for zoned stroage.
Signed-off-by: Daeho Jeong
---
v2: covered the direct io case
Oh, one more missed case, mkwrite?
Thanks,
---
So, I was wondering we can give data even in cp_error case.
On 03/12, Chao Yu wrote:
> Ping,
>
> Jaegeuk, do you have any comments on this patch?
>
> Thanks,
>
> On 2024/2/26 16:00, Chao Yu wrote:
> > Any comments?
> >
> > Thanks,
> >
> > On 2024/2/19 11:13, Chao Yu wrote:
> > > On 2024/2/8
Will check this after merge window.
On 03/12, Chao Yu wrote:
> Ping,
>
> On 2024/2/29 22:38, Chao Yu wrote:
> > Support .shutdown callback in f2fs_sops, then, it can be called to
> > shut down the file system when underlying block device is marked dead.
> >
> > Signed-off-by: Chao Yu
> > ---
>
On 03/12, Ed Tsai (蔡宗軒) wrote:
> On Mon, 2024-01-15 at 20:05 +0800, Hillf Danton wrote:
> >
> > ...
> >
> > --- x/fs/f2fs/file.c
> > +++ y/fs/f2fs/file.c
> > @@ -39,6 +39,7 @@
> > static vm_fault_t f2fs_filemap_fault(struct vm_fault *vmf)
> > {
> > struct inode *inode =
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Mon, 11 Mar 2024 16:59:19 -0700 you wrote:
> From: Daeho Jeong
>
> Since atomic write way was changed to out-place-update, we should
> prevent it on pinned files.
>
> Signed-off-by: Daeho Jeong
>
> [...]
Here is
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Mon, 11 Mar 2024 15:48:54 +0800 you wrote:
> {new,change}_curseg() may return error in some special cases,
> error handling should be did in their callers, and this will also
> facilitate subsequent error path expansion
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Fri, 8 Mar 2024 09:08:34 +0800 you wrote:
> Below race case can cause data corruption:
>
> Thread A GC thread
> - gc_data_segment
>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Wed, 6 Mar 2024 11:47:45 +0800 you wrote:
> The following f2fs_io test will get a "0" result instead of -EINVAL,
> unisoc # ./f2fs_io compress file
> unisoc # ./f2fs_io reserve_cblocks file
> 0
> it's not reasonable,
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: [f2fs-dev,1/2] f2fs: prevent atomic write on pinned file
Submitter: Daeho Jeong
Committer: Jaegeuk Kim
Patchwork:
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim :
On Fri, 8 Mar 2024 11:50:57 +0800 you wrote:
> Commit 2e2c6e9b72ce ("f2fs: remove power-of-two limitation of zoned
> device") missed to remove pow2 check condition in init_blkz_info(),
> fix it.
>
> Fixes: 2e2c6e9b72ce
From: Daeho Jeong
In a case writing without fallocate(), we can't guarantee it's allocated
in the conventional area for zoned stroage.
Signed-off-by: Daeho Jeong
---
v2: covered the direct io case
---
fs/f2fs/data.c | 14 --
fs/f2fs/file.c | 4
2 files changed, 16
On Mar 12, 2024 / 12:57, Yi Zhang wrote:
...
> Sorry, please use this one.
Thanks. I have succeeded to recreate the issue. Will take a look tomorrow.
___
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
13 matches
Mail list logo
