mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: "Thomas Weißschuh" <thomas@t-8ch.de>,
	"Jingbo Xu" <jefflexu@linux.alibaba.com>
Cc: chao@kernel.org, huyue2@coolpad.com,
	linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH v2] erofs: deprecate superblock checksum feature
Date: Sun, 30 Jul 2023 22:01:11 +0800	[thread overview]
Message-ID: <bdd94a7c-7364-c262-ed01-d7e6fcb26007@linux.alibaba.com> (raw)
In-Reply-To: <f796b2ed-8564-45c3-bb04-44dfabb575c7@t-8ch.de>


Hi Thomas,

On 2023/7/30 21:31, Thomas Weißschuh wrote:
> On 2023-07-17 19:27:03+0800, Jingbo Xu wrote:
>> Later we're going to try the self-contained image verification.
>> The current superblock checksum feature has quite limited
>> functionality, instead, merkle trees can provide better protection
>> for image integrity.
> 
> The crc32c checksum is also used by libblkid to gain more confidence
> in its filesystem detection.
> I guess a merkle tree would be much harder to implement.
> 
> This is for example used by the mount(8) cli program to allow mounting
> of devices without explicitly needing to specify a filesystem.
> 
> Note: libblkid tests for EROFS_FEATURE_SB_CSUM so at least it won't
> break when the checksum is removed.
I'm not sure if we could switch EROFS_FEATURE_SB_CSUM to a simpler
checksum instead (e.g. just sum each byte up if both
EROFS_FEATURE_SB_CSUM and COMPAT_XATTR_FILTER bits are set, or
ignore checksums completely at least in the kernel) if the better
filesystem detection by using sb chksum is needed (not sure if other
filesystems have sb chksum or just do magic comparsion)?

The main problem here is after xattr name filter feature is added
(xxhash is generally faster than crc32c), there could be two
hard-depended hashing algorithms, this increases more dependency
especially for embededed devices.

Thanks,
Gao Xiang

  reply	other threads:[~2023-07-30 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 11:27 Jingbo Xu
2023-07-17 16:16 ` Gao Xiang
2023-07-30 13:04 ` Chao Yu
2023-07-30 13:31 ` Thomas Weißschuh
2023-07-30 14:01   ` Gao Xiang [this message]
2023-07-30 14:28     ` Thomas Weißschuh
2023-07-30 14:37       ` Gao Xiang
2023-07-30 14:49         ` Thomas Weißschuh
2023-07-30 14:56           ` Gao Xiang
2023-08-01  2:47       ` Jingbo Xu

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=bdd94a7c-7364-c262-ed01-d7e6fcb26007@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=chao@kernel.org \
    --cc=huyue2@coolpad.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=kzak@redhat.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    /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

all inboxes | Powered by JetHome®