public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, daehojeong@google.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	guoxiaolong2008@gmail.com, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid mapping wrong physical block for swapfile
Date: Mon, 19 Jan 2026 13:50:45 +0000	[thread overview]
Message-ID: <176883064552.1419958.12451126631540238696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260113062229.4062-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 13 Jan 2026 14:22:29 +0800 you wrote:
> Xiaolong Guo reported a f2fs bug in bugzilla [1]
> 
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=220951
> 
> Quoted:
> 
> "When using stress-ng's swap stress test on F2FS filesystem with kernel 6.6+,
> the system experiences data corruption leading to either:
> 1 dm-verity corruption errors and device reboot
> 2 F2FS node corruption errors and boot hangs
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix to avoid mapping wrong physical block for swapfile
    https://git.kernel.org/jaegeuk/f2fs/c/5c145c03188b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-01-19 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  6:22 [PATCH] f2fs: fix to avoid mapping wrong physical block for swapfile Chao Yu
2026-01-19 13:50 ` 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=176883064552.1419958.12451126631540238696.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=daehojeong@google.com \
    --cc=guoxiaolong2008@gmail.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox