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] f2fs: support FAULT_TIMEOUT
Date: Wed, 30 Apr 2025 02:00:28 +0000 [thread overview]
Message-ID: <174597842800.1861815.12345517608809854649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250425095055.1129285-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 25 Apr 2025 17:50:55 +0800 you wrote:
> Support to inject a timeout fault into function, currently it only
> support to inject timeout to commit_atomic_write flow to reproduce
> inconsistent bug, like the bug fixed by commit f098aeba04c9 ("f2fs:
> fix to avoid atomicity corruption of atomic file").
>
> By default, the new type fault will inject 1000ms timeout, and the
> timeout process can be interrupted by SIGKILL.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: support FAULT_TIMEOUT
https://git.kernel.org/jaegeuk/f2fs/c/7724284838ee
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, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: support FAULT_TIMEOUT
Date: Wed, 30 Apr 2025 02:00:28 +0000 [thread overview]
Message-ID: <174597842800.1861815.12345517608809854649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250425095055.1129285-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 25 Apr 2025 17:50:55 +0800 you wrote:
> Support to inject a timeout fault into function, currently it only
> support to inject timeout to commit_atomic_write flow to reproduce
> inconsistent bug, like the bug fixed by commit f098aeba04c9 ("f2fs:
> fix to avoid atomicity corruption of atomic file").
>
> By default, the new type fault will inject 1000ms timeout, and the
> timeout process can be interrupted by SIGKILL.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: support FAULT_TIMEOUT
https://git.kernel.org/jaegeuk/f2fs/c/7724284838ee
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:[~2025-04-30 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 9:50 [f2fs-dev] [PATCH] f2fs: support FAULT_TIMEOUT Chao Yu via Linux-f2fs-devel
2025-04-25 9:50 ` Chao Yu
2025-04-30 2:00 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-04-30 2:00 ` [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=174597842800.1861815.12345517608809854649.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.