The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix return value of f2fs_recover_fsync_data()
Date: Tue, 11 Nov 2025 22:50:21 +0000	[thread overview]
Message-ID: <176290142149.3596344.6185023964431728544.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105065023.3656975-1-chao@kernel.org>

Hello:

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

On Wed,  5 Nov 2025 14:50:22 +0800 you wrote:
> With below scripts, it will trigger panic in f2fs:
> 
> mkfs.f2fs -f /dev/vdd
> mount /dev/vdd /mnt/f2fs
> touch /mnt/f2fs/foo
> sync
> echo 111 >> /mnt/f2fs/foo
> f2fs_io fsync /mnt/f2fs/foo
> f2fs_io shutdown 2 /mnt/f2fs
> umount /mnt/f2fs
> mount -o ro,norecovery /dev/vdd /mnt/f2fs
> or
> mount -o ro,disable_roll_forward /dev/vdd /mnt/f2fs
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/2] f2fs: fix return value of f2fs_recover_fsync_data()
    https://git.kernel.org/jaegeuk/f2fs/c/d05faa07e7da
  - [f2fs-dev,2/2] f2fs: fix to detect recoverable inode during dryrun of find_fsync_dnodes()
    https://git.kernel.org/jaegeuk/f2fs/c/ca244e9242a1

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



      parent reply	other threads:[~2025-11-11 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  6:50 [PATCH 1/2] f2fs: fix return value of f2fs_recover_fsync_data() Chao Yu
2025-11-05  6:50 ` [PATCH 2/2] f2fs: fix to detect recoverable inode during dryrun of find_fsync_dnodes() Chao Yu
2025-11-11 22: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=176290142149.3596344.6185023964431728544.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --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