From: patchwork-bot+f2fs@kernel.org
To: wangzijie <wangzijie1@honor.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org, feng.han@honor.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: fix zero-sized extent for precache extents
Date: Mon, 29 Sep 2025 22:30:34 +0000 [thread overview]
Message-ID: <175918503424.1733438.15522047521357961173.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250917023622.516052-1-wangzijie1@honor.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 17 Sep 2025 10:36:21 +0800 you wrote:
> Script to reproduce:
> f2fs_io write 1 0 1881 rand dsync testfile
> f2fs_io fallocate 0 7708672 4096 testfile
> f2fs_io write 1 1881 1 rand buffered testfile
> fsync testfile
> umount
> mount
> f2fs_io precache_extents testfile
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: fix zero-sized extent for precache extents
(no matching commit)
- [f2fs-dev,v3,2/2] f2fs: fix infinite loop in __insert_extent_tree()
https://git.kernel.org/jaegeuk/f2fs/c/23361bd54966
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:[~2025-09-29 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 2:36 wangzijie
2025-09-17 2:36 ` [f2fs-dev] [PATCH v3 2/2] f2fs: fix infinite loop in __insert_extent_tree() wangzijie
2025-09-17 6:48 ` Chao Yu
2025-09-17 6:41 ` [f2fs-dev] [PATCH v3 1/2] f2fs: fix zero-sized extent for precache extents Chao Yu
2025-09-17 15:59 ` Jaegeuk Kim
2025-09-29 22:30 ` 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=175918503424.1733438.15522047521357961173.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzijie1@honor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®