From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, v-songbaohua@oppo.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to force buffered IO on inline_data inode
Date: Wed, 12 Jun 2024 15:55:57 +0000 [thread overview]
Message-ID: <171820775729.32393.7251723492802127361.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240523132948.2250254-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 23 May 2024 21:29:48 +0800 you wrote:
> It will return all zero data when DIO reading from inline_data inode, it
> is because f2fs_iomap_begin() assign iomap->type w/ IOMAP_HOLE incorrectly
> for this case.
>
> We can let iomap framework handle inline data via assigning iomap->type
> and iomap->inline_data correctly, however, it will be a little bit
> complicated when handling race case in between direct IO and buffered IO.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to force buffered IO on inline_data inode
https://git.kernel.org/jaegeuk/f2fs/c/5c8764f8679e
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: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, v-songbaohua@oppo.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to force buffered IO on inline_data inode
Date: Wed, 12 Jun 2024 15:55:57 +0000 [thread overview]
Message-ID: <171820775729.32393.7251723492802127361.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240523132948.2250254-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 23 May 2024 21:29:48 +0800 you wrote:
> It will return all zero data when DIO reading from inline_data inode, it
> is because f2fs_iomap_begin() assign iomap->type w/ IOMAP_HOLE incorrectly
> for this case.
>
> We can let iomap framework handle inline data via assigning iomap->type
> and iomap->inline_data correctly, however, it will be a little bit
> complicated when handling race case in between direct IO and buffered IO.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to force buffered IO on inline_data inode
https://git.kernel.org/jaegeuk/f2fs/c/5c8764f8679e
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-06-12 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 13:29 [f2fs-dev] [PATCH] f2fs: fix to force buffered IO on inline_data inode Chao Yu
2024-05-23 13:29 ` Chao Yu
2024-06-12 15:55 ` patchwork-bot+f2fs [this message]
2024-06-12 15:55 ` [f2fs-dev] " patchwork-bot+f2fs
[not found] <CGME20241031050939epcms2p7971f1cc52ea141d4a7b29d68427c2fd6@epcms2p7>
[not found] ` <20241031050939epcms2p7971f1cc52ea141d4a7b29d68427c2fd6@epcms2p7>
2024-11-01 3:20 ` Chao Yu via Linux-f2fs-devel
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=171820775729.32393.7251723492802127361.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 \
--cc=stable@vger.kernel.org \
--cc=v-songbaohua@oppo.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.