Re: [f2fs-dev] [PATCH 00/12] acl: remove remaining posix acl handlers

2023-01-30 Thread Christian Brauner
On Wed, Jan 25, 2023 at 12:28:45PM +0100, Christian Brauner wrote: > Hey everyone, > > after we finished the introduction of the new posix acl api last cycle > we still left the generic POSIX ACL xattr handler around for two > reasons. First, because a few filesystems relied on the ->list() method

Re: [f2fs-dev] [PATCH 00/12] acl: remove remaining posix acl handlers

2023-01-30 Thread Christoph Hellwig
On Mon, Jan 30, 2023 at 10:10:52AM +0100, Christian Brauner wrote: > However, a few filesystems still rely on the ->list() method of the > generix POSIX ACL xattr handlers in their ->listxattr() inode operation. > This is a very limited set of filesystems. For most of them there is no > dependence

Re: [f2fs-dev] [PATCH 00/12] acl: remove remaining posix acl handlers

2023-01-30 Thread Christian Brauner
On Mon, Jan 30, 2023 at 10:16:15AM +0100, Christoph Hellwig wrote: > On Mon, Jan 30, 2023 at 10:10:52AM +0100, Christian Brauner wrote: > > However, a few filesystems still rely on the ->list() method of the > > generix POSIX ACL xattr handlers in their ->listxattr() inode operation. > > This is a

Re: [f2fs-dev] [PATCH] f2fs: synchronize atomic write aborts

2023-01-30 Thread Daeho Jeong
Hi Chao, I read your patch series now and I like it. However, how about a race condition between start_atomic_write and abort_atomic_write? abort_atomic_write is called without inode_lock in closing filp scenarios. What do you think about this? Thanks, On Fri, Jan 27, 2023 at 6:07 PM Chao Yu w

[f2fs-dev] [PATCH v2 0/8] acl: remove generic posix acl handlers from all xattr handlers

2023-01-30 Thread Christian Brauner
Hey everyone, after we finished the introduction of the new posix acl api last cycle we still left the generic POSIX ACL xattr handlers around in the filesystems xattr handler registered at sb->s_xattr for two reasons. First, because a few filesystems rely on the ->list() method of the generic POS

[f2fs-dev] [PATCH v2 6/8] fs: simplify ->listxattr() implementation

2023-01-30 Thread Christian Brauner
The ext{2,4}, erofs, f2fs, and jffs2 filesystems use the same logic to check whether a given xattr can be listed. Simplify them and avoid open-coding the same check by calling the helper we introduced earlier. Cc: linux-f2fs-devel@lists.sourceforge.net Cc: linux-er...@lists.ozlabs.org Cc: linux-e.

Re: [f2fs-dev] [PATCH v2 6/8] fs: simplify ->listxattr() implementation

2023-01-30 Thread Christoph Hellwig
Looks good: Reviewed-by: Christoph Hellwig ___ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Re: [f2fs-dev] [PATCH] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-01-30 Thread Jaegeuk Kim
On 01/28, Chao Yu wrote: > On 2023/1/5 12:22, Yangtao Li wrote: > > Convert to use iostat_lat_type as parameter instead of raw number. > > BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, and rename > > iotype to page_type to match the definition. > > > > Signed-off-by: Yangtao Li > > --- >

Re: [f2fs-dev] [PATCH] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-01-30 Thread Jaegeuk Kim
On 01/30, Jaegeuk Kim wrote: > On 01/28, Chao Yu wrote: > > On 2023/1/5 12:22, Yangtao Li wrote: > > > Convert to use iostat_lat_type as parameter instead of raw number. > > > BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, and rename > > > iotype to page_type to match the definition. > > >

Re: [f2fs-dev] [PATCH 1/4] f2fs: fix to set ipu policy

2023-01-30 Thread Jaegeuk Kim
Please adjust the comments based on v2. On 01/28, Chao Yu wrote: > On 2023/1/20 21:40, Yangtao Li wrote: > > For LFS mode, it should update outplace and no need inplace update. > > When using LFS mode for small-volume devices, IPU will not be used, > > and the OPU writing method is actually used,

Re: [f2fs-dev] [PATCH] f2fs: drop useless initializer and unneeded local variable

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Thu, 22 Dec 2022 16:18:55 +0800 you wrote: > No need to initialize idx twice. BTW, remove the unnecessary cnt variable. > > Signed-off-by: Yangtao Li > --- > fs/f2fs/iostat.c | 10 -- > 1 file changed, 4 insert

Re: [f2fs-dev] [PATCH 1/3] f2fs: clarify compress level bit offset

2023-01-30 Thread patchwork-bot+f2fs
Hello: This series was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Thu, 12 Jan 2023 21:34:43 +0800 you wrote: > commit 3fde13f817e2 ("f2fs: compress: support compress level") introduce > compress level, which macro(COMPRESS_LEVEL_OFFSET) is 8, But use wrong > comment about compress leve

Re: [f2fs-dev] [PATCH] f2fs: allow set compression option of files without blocks

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 23 Jan 2023 17:46:01 +0800 you wrote: > Files created by truncate have a size but no blocks, so > they can be allowed to set compression option. > > Fixes: e1e8debec656 ("f2fs: add F2FS_IOC_SET_COMPRESS_OPTION ioctl

Re: [f2fs-dev] [PATCH] f2fs: remove unneeded f2fs_cp_error() in f2fs_create_whiteout()

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 9 Jan 2023 11:47:34 +0800 you wrote: > f2fs_rename() has checked CP_ERROR_FLAG, so remove redundant check > in f2fs_create_whiteout(). > > Signed-off-by: Chao Yu > --- > fs/f2fs/namei.c | 3 --- > 1 file changed,

Re: [f2fs-dev] [PATCH v2] f2fs: fix to check warm_data_age_threshold

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Tue, 17 Jan 2023 21:24:42 +0800 you wrote: > hot_data_age_threshold is a non-zero positive number, and > condition 2 includes condition 1, so there is no need to > additionally judge whether t is 0. And let's remove it. >

Re: [f2fs-dev] [PATCH] f2fs: fix to show discard_unit mount opt

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 16 Jan 2023 22:12:28 +0800 you wrote: > Convert to show discard_unit only when has DISCARD opt. > > Signed-off-by: Yangtao Li > --- > fs/f2fs/super.c | 18 +- > 1 file changed, 9 insertions(+), 9 d

Re: [f2fs-dev] [PATCH 1/5] f2fs: introduce trace_f2fs_replace_atomic_write_block

2023-01-30 Thread patchwork-bot+f2fs
Hello: This series was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 9 Jan 2023 11:44:49 +0800 you wrote: > Commit 3db1de0e582c ("f2fs: change the current atomic write way") > removed old tracepoints, but it missed to add new one, this patch > fixes to introduce trace_f2fs_replace_a

[f2fs-dev] Patchwork summary for: f2fs

2023-01-30 Thread patchwork-bot+f2fs
Hello: The following patches were marked "accepted", because they were applied to jaegeuk/f2fs.git (dev): Series: [f2fs-dev,1/5] f2fs: introduce trace_f2fs_replace_atomic_write_block Submitter: Chao Yu Committer: Jaegeuk Kim Patchwork: https://patchwork.kernel.org/project/f2fs/list/?serie

Re: [f2fs-dev] [PATCH 4/8] f2fs: factor the read/write tracing logic into a helper

2023-01-30 Thread Jaegeuk Kim
On 01/29, Chao Yu wrote: > On 2023/1/19 14:36, Christoph Hellwig wrote: > > Factor the logic to log a path for reads and writs into a helper > > shared between the read_iter and write_iter methods. > > > > Signed-off-by: Christoph Hellwig > > --- > > fs/f2fs/file.c | 60 +---

Re: [f2fs-dev] [PATCH] f2fs: return true if all cmd were issued or no cmd need to be issued for f2fs_issue_discard_timeout()

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Fri, 13 Jan 2023 03:14:04 +0800 you wrote: > f2fs_issue_discard_timeout() returns whether discard cmds are dropped, > which does not match the meaning of the function. Let's change it to > return whether all discard cmd a

Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity check on extent cache correctly

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 9 Jan 2023 11:49:20 +0800 you wrote: > In do_read_inode(), sanity_check_inode() should be called after > f2fs_init_read_extent_tree(), fix it. > > Fixes: 728400a1 ("f2fs: allocate the extent_cache by default")

Re: [f2fs-dev] [PATCH] f2fs: fix information leak in f2fs_move_inline_dirents()

2023-01-30 Thread patchwork-bot+f2fs
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Sun, 22 Jan 2023 23:04:14 -0800 you wrote: > From: Eric Biggers > > When converting an inline directory to a regular one, f2fs is leaking > uninitialized memory to disk because it doesn't initialize the entire > directo

Re: [f2fs-dev] [PATCH v3] f2fs: retry to update the inode page given EIO

2023-01-30 Thread Jaegeuk Kim
If the storage gives a corrupted node block due to short power failure and reset, f2fs stops the entire operations by setting the checkpoint failure flag. Let's give more chances to live by re-issuing IOs for a while in such critical path. Cc: sta...@vger.kernel.org Suggested-by: Randall Huang S

Re: [f2fs-dev] [PATCH v2] f2fs: retry to update the inode page given EIO

2023-01-30 Thread Jaegeuk Kim
On 01/28, Chao Yu wrote: > On 2023/1/13 8:01, Jaegeuk Kim wrote: > > On 01/12, Chao Yu wrote: > > > On 2023/1/12 2:50, Jaegeuk Kim wrote: > > > > On 01/11, Chao Yu wrote: > > > > > On 2023/1/11 9:20, Jaegeuk Kim wrote: > > > > > > In f2fs_update_inode_page, f2fs_get_node_page handles EIO along with

Re: [f2fs-dev] [PATCH v3 1/2] f2fs: fix to avoid potential memory corruption in __update_iostat_latency()

2023-01-30 Thread Chao Yu
On 2023/1/21 0:16, Yangtao Li wrote: Add iotype sanity check to avoid potential memory corruption. This is to fix the compile error below: fs/f2fs/iostat.c:231 __update_iostat_latency() error: buffer overflow 'io_lat->peak_lat[type]' 3 <= 3 vim +228 fs/f2fs/iostat.c 211 static inline void

Re: [f2fs-dev] [PATCH v3 2/2] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-01-30 Thread Chao Yu
On 2023/1/21 0:16, Yangtao Li wrote: Convert to use iostat_lat_type as parameter instead of raw number. BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, and rename iotype to page_type to match the definition. Reported-by: kernel test robot Reported-by: Dan Carpenter Signed-off-by: Yangta

Re: [f2fs-dev] [PATCH] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-01-30 Thread Chao Yu
On 2023/1/31 5:35, Jaegeuk Kim wrote: On 01/28, Chao Yu wrote: On 2023/1/5 12:22, Yangtao Li wrote: Convert to use iostat_lat_type as parameter instead of raw number. BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, and rename iotype to page_type to match the definition. Signed-off-by: Y

Re: [f2fs-dev] [PATCH] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-01-30 Thread Chao Yu
On 2023/1/31 6:23, Jaegeuk Kim wrote: On 01/30, Jaegeuk Kim wrote: On 01/28, Chao Yu wrote: On 2023/1/5 12:22, Yangtao Li wrote: Convert to use iostat_lat_type as parameter instead of raw number. BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, and rename iotype to page_type to match the

Re: [f2fs-dev] [PATCH v2 2/5] f2fs: fix to set ipu policy

2023-01-30 Thread Chao Yu
On 2023/1/21 13:12, Yangtao Li wrote: For LFS mode, it should update outplace and no need inplace update. When using LFS mode for small-volume devices, IPU will not be used, and the OPU writing method is actually used, but F2FS_IPU_FORCE can be read from the ipu_policy node, which is different fr

[f2fs-dev] [PATCH] f2fs: clean up parameters of iostat_update_and_unbind_ctx()

2023-01-30 Thread Chao Yu
Parsing sync/rw type from bio inside iostat_update_and_unbind_ctx() to avoid unnecessary parameters. Signed-off-by: Chao Yu --- - this patch is based on [PATCH v3] f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx() fs/f2fs/data.c | 4 ++-- fs/f2fs/iostat.

Re: [f2fs-dev] [PATCH v3] f2fs: retry to update the inode page given EIO

2023-01-30 Thread Chao Yu
On 2023/1/31 7:30, Jaegeuk Kim wrote: If the storage gives a corrupted node block due to short power failure and reset, f2fs stops the entire operations by setting the checkpoint failure flag. Let's give more chances to live by re-issuing IOs for a while in such critical path. Cc: sta...@vger.k