From: patchwork-bot+f2fs@kernel.org
To: Xiuhong Wang <xiuhong.wang@unisoc.com>
Cc: hongyu.jin.cn@gmail.com, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
xiuhong.wang.cn@gmail.com, jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH V2 1/2] f2fs: compress: relocate some judgments in f2fs_reserve_compress_blocks
Date: Wed, 13 Mar 2024 01:30:29 +0000 [thread overview]
Message-ID: <171029342995.17296.13814508095953932881.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240306034746.3722986-1-xiuhong.wang@unisoc.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
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, so the judgement of
> atomic_read(&F2FS_I(inode)->i_compr_blocks) should be placed after
> the judgement of is_inode_flag_set(inode, FI_COMPRESS_RELEASED).
>
> [...]
Here is the summary with links:
- [f2fs-dev,V2,1/2] f2fs: compress: relocate some judgments in f2fs_reserve_compress_blocks
https://git.kernel.org/jaegeuk/f2fs/c/b7d797d241c1
- [f2fs-dev,V2,2/2] f2fs: compress: fix reserve_cblocks counting error when out of space
https://git.kernel.org/jaegeuk/f2fs/c/2f6d721e14b6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Xiuhong Wang <xiuhong.wang@unisoc.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, ke.wang@unisoc.com,
xiuhong.wang.cn@gmail.com, hongyu.jin.cn@gmail.com
Subject: Re: [f2fs-dev] [PATCH V2 1/2] f2fs: compress: relocate some judgments in f2fs_reserve_compress_blocks
Date: Wed, 13 Mar 2024 01:30:29 +0000 [thread overview]
Message-ID: <171029342995.17296.13814508095953932881.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240306034746.3722986-1-xiuhong.wang@unisoc.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
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, so the judgement of
> atomic_read(&F2FS_I(inode)->i_compr_blocks) should be placed after
> the judgement of is_inode_flag_set(inode, FI_COMPRESS_RELEASED).
>
> [...]
Here is the summary with links:
- [f2fs-dev,V2,1/2] f2fs: compress: relocate some judgments in f2fs_reserve_compress_blocks
https://git.kernel.org/jaegeuk/f2fs/c/b7d797d241c1
- [f2fs-dev,V2,2/2] f2fs: compress: fix reserve_cblocks counting error when out of space
https://git.kernel.org/jaegeuk/f2fs/c/2f6d721e14b6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-03-13 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 3:47 [f2fs-dev] [PATCH V2 1/2] f2fs: compress: relocate some judgments in f2fs_reserve_compress_blocks Xiuhong Wang
2024-03-06 3:47 ` Xiuhong Wang
2024-03-06 3:47 ` [f2fs-dev] [PATCH V2 2/2] f2fs: compress: fix reserve_cblocks counting error when out of space Xiuhong Wang
2024-03-06 3:47 ` Xiuhong Wang
2024-03-06 6:01 ` [f2fs-dev] " Chao Yu
2024-03-06 6:01 ` Chao Yu
2024-03-06 6:01 ` [f2fs-dev] [PATCH V2 1/2] f2fs: compress: relocate some judgments in f2fs_reserve_compress_blocks Chao Yu
2024-03-06 6:01 ` Chao Yu
2024-03-13 1:30 ` patchwork-bot+f2fs [this message]
2024-03-13 1:30 ` [f2fs-dev] " patchwork-bot+f2fs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171029342995.17296.13814508095953932881.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=hongyu.jin.cn@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xiuhong.wang.cn@gmail.com \
--cc=xiuhong.wang@unisoc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.