mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
	ke.wang@unisoc.com, Hao_hao.Wang@unisoc.com
Subject: Re: [PATCH] f2fs: fix to avoid changing 'check only' behaior of recovery
Date: Wed, 22 Jan 2025 14:27:42 +0800	[thread overview]
Message-ID: <9edcabc6-bfaa-48ea-ab59-54180d6c62c7@kernel.org> (raw)
In-Reply-To: <1737425741-3004-1-git-send-email-zhiguo.niu@unisoc.com>

On 1/21/25 10:15, Zhiguo Niu wrote:
> The following two 'check only recovery' processes are very dependent on
> the return value of f2fs_recover_fsync_data, especially when the return
> value is greater than 0.
> 1. when device has readonly mode, shown as commit
> 23738e74472f ("f2fs: fix to restrict mount condition on readonly block device")
> 2. mount optiont NORECOVERY or DISABLE_ROLL_FORWARD is set, shown as commit
> 6781eabba1bd ("f2fs: give -EINVAL for norecovery and rw mount")
> 
> However, commit c426d99127b1 ("f2fs: Check write pointer consistency of open zones")
> will change the return value unexpectedly, thereby changing the caller's behavior
> 
> This patch let the f2fs_recover_fsync_data return correct value,and not do
> f2fs_check_and_fix_write_pointer when the device is read-only.
> 
> Fixes: c426d99127b1 ("f2fs: Check write pointer consistency of open zones")
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

      reply	other threads:[~2025-01-22  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  2:15 Zhiguo Niu
2025-01-22  6:27 ` Chao Yu [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=9edcabc6-bfaa-48ea-ab59-54180d6c62c7@kernel.org \
    --to=chao@kernel.org \
    --cc=Hao_hao.Wang@unisoc.com \
    --cc=jaegeuk@kernel.org \
    --cc=ke.wang@unisoc.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niuzhiguo84@gmail.com \
    --cc=zhiguo.niu@unisoc.com \
    /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

all inboxes | Powered by JetHome®