From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to recover quota data correctly
Date: Wed, 12 Apr 2023 16:20:19 +0000 [thread overview]
Message-ID: <168131641904.15557.7224086713255348466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230402112706.42211-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 2 Apr 2023 19:27:06 +0800 you wrote:
> With -O quota mkfs option, xfstests generic/417 fails due to fsck detects
> data corruption on quota inodes.
>
> [ASSERT] (fsck_chk_quota_files:2051) --> Quota file is missing or invalid quota file content found.
>
> The root cause is there is a hole f2fs doesn't hold quota inodes,
> so all recovered quota data will be dropped due to SBI_POR_DOING
> flag was set.
> - f2fs_fill_super
> - f2fs_recover_orphan_inodes
> - f2fs_enable_quota_files
> - f2fs_quota_off_umount
> <--- quota inodes were dropped --->
> - f2fs_recover_fsync_data
> - f2fs_enable_quota_files
> - f2fs_quota_off_umount
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to recover quota data correctly
https://git.kernel.org/jaegeuk/f2fs/c/cbb356d60c54
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-12 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 11:27 [PATCH] f2fs: fix to recover quota data correctly Chao Yu
2023-04-12 16:20 ` 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=168131641904.15557.7224086713255348466.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 \
/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