From: "Jeff Brasen" <jbrasen@nvidia.com>
To: <devel@edk2.groups.io>
Cc: <pedro.falcato@gmail.com>, Jeff Brasen <jbrasen@nvidia.com>
Subject: [PATCH v2 2/2] Ext4Pkg: Support uncleanly unmounted filesystems
Date: Fri, 10 Sep 2021 15:58:39 +0000 [thread overview]
Message-ID: <330849752fdf246f7182db697be6f62f5cc335a3.1631289393.git.jbrasen@nvidia.com> (raw)
In-Reply-To: <cover.1631289393.git.jbrasen@nvidia.com>
Support for uncleanly mounted filesystems, if there is a recovery
journal mark filesystem as read-only.
Signed-off-by: Jeff Brasen <jbrasen@nvidia.com>
---
Features/Ext4Pkg/Ext4Dxe/Superblock.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/Features/Ext4Pkg/Ext4Dxe/Superblock.c b/Features/Ext4Pkg/Ext4Dxe/Superblock.c
index 1ceb0d5cbb..251babb320 100644
--- a/Features/Ext4Pkg/Ext4Dxe/Superblock.c
+++ b/Features/Ext4Pkg/Ext4Dxe/Superblock.c
@@ -18,7 +18,7 @@ STATIC CONST UINT32 gSupportedIncompatFeat =
EXT4_FEATURE_INCOMPAT_64BIT | EXT4_FEATURE_INCOMPAT_DIRDATA |
EXT4_FEATURE_INCOMPAT_FLEX_BG | EXT4_FEATURE_INCOMPAT_FILETYPE |
EXT4_FEATURE_INCOMPAT_EXTENTS | EXT4_FEATURE_INCOMPAT_LARGEDIR |
- EXT4_FEATURE_INCOMPAT_MMP;
+ EXT4_FEATURE_INCOMPAT_MMP | EXT4_FEATURE_INCOMPAT_RECOVER;
// Future features that may be nice additions in the future:
// 1) Btree support: Required for write support and would speed up lookups in large directories.
@@ -89,10 +89,8 @@ Ext4SuperblockValidate (
return FALSE;
}
- // Is this correct behaviour? Imagine the power cuts out, should the system fail to boot because
- // we're scared of touching something corrupt?
if ((Sb->s_state & EXT4_FS_STATE_UNMOUNTED) == 0) {
- return FALSE;
+ DEBUG ((DEBUG_WARN, "[ext4] Filesystem was not unmounted cleanly\n"));
}
return TRUE;
@@ -215,6 +213,11 @@ Ext4OpenSuperblock (
return EFI_UNSUPPORTED;
}
+ if (EXT4_HAS_INCOMPAT (Partition, EXT4_FEATURE_INCOMPAT_RECOVER)) {
+ DEBUG ((DEBUG_WARN, "[ext4] Needs journal recovery, mounting read-only\n"));
+ Partition->ReadOnly = TRUE;
+ }
+
// At the time of writing, it's the only supported checksum.
if (Partition->FeaturesCompat & EXT4_FEATURE_RO_COMPAT_METADATA_CSUM &&
Sb->s_checksum_type != EXT4_CHECKSUM_CRC32C) {
--
2.17.1
prev parent reply other threads:[~2021-09-10 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 15:58 [PATCH v2 0/2] ExtPkg Updates Jeff Brasen
2021-09-10 15:58 ` [PATCH v2 1/2] Ext4Pkg: Improve Ext4IsBindingSupported() behavior Jeff Brasen
2021-09-10 16:52 ` Pedro Falcato
2021-09-10 16:56 ` [edk2-devel] " Marvin Häuser
2021-09-10 17:05 ` Jeff Brasen
2021-09-10 17:08 ` Pedro Falcato
2021-09-10 18:09 ` Marvin Häuser
2021-09-10 21:07 ` Jeff Brasen
2021-09-10 15:58 ` Jeff Brasen [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-list 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=330849752fdf246f7182db697be6f62f5cc335a3.1631289393.git.jbrasen@nvidia.com \
--to=devel@edk2.groups.io \
/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