From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH 1/2] sload.f2fs: fix missing fsck_init
Date: Wed, 15 Jul 2020 10:30:16 -0700 [thread overview]
Message-ID: <20200715173017.1887640-1-jaegeuk@kernel.org> (raw)
This patch allocates some data structures that will be used for loading files
on existing image.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fsck/sload.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fsck/sload.c b/fsck/sload.c
index c064f7f..59ba4a6 100644
--- a/fsck/sload.c
+++ b/fsck/sload.c
@@ -313,6 +313,9 @@ int f2fs_sload(struct f2fs_sb_info *sbi)
{
int ret = 0;
+ /* this requires for the below sanity checks */
+ fsck_init(sbi);
+
ret = configure_files();
if (ret) {
ERR_MSG("Failed to configure files\n");
--
2.27.0.389.gc38d7665816-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2020-07-15 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 17:30 Jaegeuk Kim [this message]
2020-07-15 17:30 ` [f2fs-dev] [PATCH 2/2] dump.f2fs: check block address first before reading the block Jaegeuk Kim
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=20200715173017.1887640-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).