linux-kernel - erofs: Question on unused fields in on-disk structs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1323459733.69859.1566234633793.JavaMail.zimbra@nod.at>
Date:   Mon, 19 Aug 2019 19:10:33 +0200 (CEST)
From:   Richard Weinberger <richard@....at>
To:     linux-erofs@...ts.ozlabs.org
Cc:     gaoxiang25@...wei.com, linux-fsdevel@...r.kernel.org,
        yuchao0@...wei.com, linux-kernel <linux-kernel@...r.kernel.org>
Subject: erofs: Question on unused fields in on-disk structs

Hi!

struct erofs_super_block has "checksum" and "features" fields,
but they are not used in the source.
What is the plan for these?

Same for i_checksum in erofs_inode_v1 and erofs_inode_v2.

At least the "features" field in the super block is something I'd
expect to be used.
...such that you can have new filesystem features in future.

Thanks,
//richard