From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to relocate check condition in f2fs_fallocate()
Date: Sun, 14 Apr 2024 15:32:45 +0000 [thread overview]
Message-ID: <171310876517.3156.14366722531397621692.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240403142420.2042498-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 3 Apr 2024 22:24:19 +0800 you wrote:
> compress and pinfile flag should be checked after inode lock held to
> avoid race condition, fix it.
>
> Fixes: 4c8ff7095bef ("f2fs: support data compression")
> Fixes: 5fed0be8583f ("f2fs: do not allow partial truncation on pinned file")
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to relocate check condition in f2fs_fallocate()
https://git.kernel.org/jaegeuk/f2fs/c/278a6253a673
- [f2fs-dev,2/2] f2fs: fix to check pinfile flag in f2fs_move_file_range()
https://git.kernel.org/jaegeuk/f2fs/c/e07230da0500
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-14 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 14:24 [PATCH 1/2] f2fs: fix to relocate check condition in f2fs_fallocate() Chao Yu
2024-04-03 14:24 ` [PATCH 2/2] f2fs: fix to check pinfile flag in f2fs_move_file_range() Chao Yu
2024-04-07 2:11 ` [f2fs-dev] [PATCH 1/2] f2fs: fix to relocate check condition in f2fs_fallocate() Zhiguo Niu
2024-04-07 7:29 ` Chao Yu
2024-04-07 8:29 ` Zhiguo Niu
2024-04-14 15:32 ` patchwork-bot+f2fs [this message]
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=171310876517.3156.14366722531397621692.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox