From: Mihai Moldovan <ionic@ionic.de>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Javier Martinez Canillas <javierm@redhat.com>
Subject: Re: [PATCH] fs/ext2: Ignore checksum seed incompat feature support
Date: Sat, 12 Jun 2021 15:55:57 +0200 [thread overview]
Message-ID: <5025fe63-d7db-210e-f66e-8e0982c22301@ionic.de> (raw)
In-Reply-To: <20210611193616.2596290-1-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
* On 6/11/21 9:36 PM, Javier Martinez Canillas wrote:
> This incompat feature is used to denote that the filesystem stored its
> metadata checksum seed in the superblock. This is used to allow tune2fs
> to change the UUID on a mounted metadata_csum filesystem without having
> to rewrite all the disk metadata.
>
> But GRUB doesn't use the metadata checksum in anyway, so can just ignore
any way
> this feature if is enabled. This is consistent with GRUB filesystem code
if it is
> in general which just does a best effort to access the filesystem's data.
>
> It may be removed from the ignored list in the future if supports to do
> metadata checksumming verification is added to the read-only FS driver.
support
or better yet:
support for
metadata checksum verification
Mihai
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-06-12 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 19:36 [PATCH] fs/ext2: Ignore checksum seed incompat feature support Javier Martinez Canillas
2021-06-12 13:55 ` Mihai Moldovan [this message]
2021-06-14 13:03 ` Lukas Czerner
2021-07-07 13:22 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2023-08-24 22:08 Stéphane Fontaine
2023-08-24 23:24 ` Vladimir 'phcoder' Serbinenko
2023-08-29 14:09 ` Daniel Kiper
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=5025fe63-d7db-210e-f66e-8e0982c22301@ionic.de \
--to=ionic@ionic.de \
--cc=grub-devel@gnu.org \
--cc=javierm@redhat.com \
/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.