From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, jprusakowski@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix potential deadloop in prepare_compress_overwrite()
Date: Tue, 04 Mar 2025 17:10:46 +0000 [thread overview]
Message-ID: <174110824699.224349.2815838938637655716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303032329.1309786-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 3 Mar 2025 11:23:29 +0800 you wrote:
> Jan Prusakowski reported a kernel hang issue as below:
>
> When running xfstests on linux-next kernel (6.14.0-rc3, 6.12) I
> encountered a problem in generic/475 test where fsstress process
> gets blocked in __f2fs_write_data_pages() and the test hangs.
> The options I used are:
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix potential deadloop in prepare_compress_overwrite()
https://git.kernel.org/jaegeuk/f2fs/c/3147ee567dd9
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, jprusakowski@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix potential deadloop in prepare_compress_overwrite()
Date: Tue, 04 Mar 2025 17:10:46 +0000 [thread overview]
Message-ID: <174110824699.224349.2815838938637655716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303032329.1309786-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 3 Mar 2025 11:23:29 +0800 you wrote:
> Jan Prusakowski reported a kernel hang issue as below:
>
> When running xfstests on linux-next kernel (6.14.0-rc3, 6.12) I
> encountered a problem in generic/475 test where fsstress process
> gets blocked in __f2fs_write_data_pages() and the test hangs.
> The options I used are:
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix potential deadloop in prepare_compress_overwrite()
https://git.kernel.org/jaegeuk/f2fs/c/3147ee567dd9
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-03-04 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 3:23 [f2fs-dev] [PATCH] f2fs: fix potential deadloop in prepare_compress_overwrite() Chao Yu via Linux-f2fs-devel
2025-03-03 3:23 ` Chao Yu
2025-03-04 17:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-03-04 17:10 ` [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=174110824699.224349.2815838938637655716.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jprusakowski@google.com \
--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.