From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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] Revert "f2fs: skip node_change lock for inline data writes"
Date: Tue, 13 Oct 2026 22:30:19 +0000 [thread overview]
Message-ID: <179193061951.1493834.15484105620575468215.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007101738.2348038-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 7 Oct 2026 10:17:38 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> This reverts commit 66eec36c2421383e5b32e9c1740f656474c80df8.
>
> Fault injection + shutdown stress test reports inconsistent inline
> data after "f2fs_io shutdown 2" (mode=lfs, nonzone, segs=1):
>
> [...]
Here is the summary with links:
- [f2fs-dev] Revert "f2fs: skip node_change lock for inline data writes"
https://git.kernel.org/jaegeuk/f2fs/c/5edbb590dbd7
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
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:17 [f2fs-dev] [PATCH] Revert "f2fs: skip node_change lock for inline data writes" Chao Yu via Linux-f2fs-devel
2026-10-07 13:50 ` Seongjae Jeong
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=179193061951.1493834.15484105620575468215.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 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.