Re: [PATCH v3] jbd2: Fix block tag checksum verification brokenness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Fortunately metadata checksumming is still "experimental" and not in a shipping
> e2fsprogs, so there should be few users affected by this.

Am I reading this patch correctly that this changes which half of
the 32-bit checksum is stored on little-endian (e.g. x86) machines?
Before, it stored the low 16 bits of cpu_to_be32(csum), meaning the
high 16 bits of csum.

Now, it's cpu_to_be16(csum32), which is the low 16 bits of csum32.

It so happens that I have multiple metadata_csum file systems.
(I enabled it a while ago on a machine where I wasn't sure if corruption
was RAM or disk, and have been using it on SSE4.2 machines since.)

Is there an upgrade path?  Also, what's the corresponding e2fsprogs
commit that supports this change?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux