From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: Jeff Brasen <jbrasen@nvidia.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [PATCH 0/2] ExtPkg Updates
Date: Fri, 10 Sep 2021 05:40:28 +0100 [thread overview]
Message-ID: <CAKbZUD0NEMxc4S0eMG5RZmDKpE52Rx=ju=UjtTkYb_wyeJBgUg@mail.gmail.com> (raw)
In-Reply-To: <cover.1631219610.git.jbrasen@nvidia.com>
Hi Jeff,
Thanks for the patches! It's great that Ext4Pkg is already getting used!
I've looked at each patch and replied with feedback.
In general, they look good, although there are some minor issues. I
hadn't thought of the 1st patch but the 2nd seemed inevitable
for real world systems that may not unmount cleanly.
Best regards,
Pedro
On Thu, Sep 9, 2021 at 9:41 PM Jeff Brasen <jbrasen@nvidia.com> wrote:
>
> I have been using the new Ext4Pkg and been pretty successful and it is solving a use case we had.
>
> Had a couple updates to propose
>
> 1. Changed the implementation of the binding protocol to both check if the driver is already bound
> to the partition as well as added a really quick check to validate the magic value in supported.
> This improves performance when you have a large number of non-ext4 partitions on the system.
>
> 2. As we are planning on using this for boot support we want to support unclean filesystem states in
> case the user doesn't reset cleanly. I added a check if the recovery journal is present and if so treat
> the filesystem as read-only (I know the driver is only RO at this point, but figured if you added write
> support prior to recovery journal support we would want that). With this everything seems to work great.
> I can add this under a FeaturePcd if desired as well.
>
> Change log
>
> v1 - Initial revision
>
> Jeff Brasen (2):
> Ext4Pkg: Improve Binding support behavior
> Ext4Pkg: Support non-cleanlty unmounted filesystems
>
> Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.h | 14 +++++++
> Features/Ext4Pkg/Ext4Dxe/Ext4Dxe.c | 57 +++++++++++++++++++++------
> Features/Ext4Pkg/Ext4Dxe/Superblock.c | 45 +++++++++++++++++++--
> 3 files changed, 99 insertions(+), 17 deletions(-)
>
> --
> 2.17.1
>
--
Pedro Falcato
prev parent reply other threads:[~2021-09-10 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 20:40 [PATCH 0/2] ExtPkg Updates Jeff Brasen
2021-09-09 20:41 ` [PATCH 1/2] Ext4Pkg: Improve Binding support behavior Jeff Brasen
2021-09-10 4:22 ` Pedro Falcato
2021-09-10 4:34 ` Jeff Brasen
2021-09-10 16:24 ` [edk2-devel] " Marvin Häuser
2021-09-09 20:41 ` [PATCH 2/2] Ext4Pkg: Support non-cleanlty unmounted filesystems Jeff Brasen
2021-09-10 4:35 ` Pedro Falcato
2021-09-10 4:40 ` Pedro Falcato [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='CAKbZUD0NEMxc4S0eMG5RZmDKpE52Rx=ju=UjtTkYb_wyeJBgUg@mail.gmail.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