From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: do not return EFSCORRUPTED, but try to run online repair
Date: Mon, 23 Oct 2023 15:30:25 +0000 [thread overview]
Message-ID: <169807502523.26537.10004934909406083909.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231019225300.1846362-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 19 Oct 2023 15:53:00 -0700 you wrote:
> If we return the error, there's no way to recover the status as of now, since
> fsck does not fix the xattr boundary issue.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/node.c | 4 +++-
> fs/f2fs/xattr.c | 20 +++++++++++++-------
> 2 files changed, 16 insertions(+), 8 deletions(-)
Here is the summary with links:
- [f2fs-dev] f2fs: do not return EFSCORRUPTED, but try to run online repair
https://git.kernel.org/jaegeuk/f2fs/c/50a472bbc79f
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: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: do not return EFSCORRUPTED, but try to run online repair
Date: Mon, 23 Oct 2023 15:30:25 +0000 [thread overview]
Message-ID: <169807502523.26537.10004934909406083909.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231019225300.1846362-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 19 Oct 2023 15:53:00 -0700 you wrote:
> If we return the error, there's no way to recover the status as of now, since
> fsck does not fix the xattr boundary issue.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/node.c | 4 +++-
> fs/f2fs/xattr.c | 20 +++++++++++++-------
> 2 files changed, 16 insertions(+), 8 deletions(-)
Here is the summary with links:
- [f2fs-dev] f2fs: do not return EFSCORRUPTED, but try to run online repair
https://git.kernel.org/jaegeuk/f2fs/c/50a472bbc79f
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:[~2023-10-23 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 22:53 [f2fs-dev] [PATCH] f2fs: do not return EFSCORRUPTED, but try to run online repair Jaegeuk Kim
2023-10-19 22:53 ` Jaegeuk Kim
2023-10-23 15:30 ` patchwork-bot+f2fs [this message]
2023-10-23 15:30 ` [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=169807502523.26537.10004934909406083909.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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.