erofs: on-disk format should have explicitly assigned numbers

As Christoph suggested [1], on-disk format should have
explicitly assigned numbers.

[1] https://lore.kernel.org/r/20190829095954.GB20598@infradead.org/
Reported-by: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
Link: https://lore.kernel.org/r/20190904020912.63925-3-gaoxiang25@huawei.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Gao Xiang 2019-09-04 10:08:49 +08:00 committed by Greg Kroah-Hartman
parent 4b66eb51d2
commit 60a49ba8fe
1 changed files with 9 additions and 9 deletions

View File

@ -53,10 +53,10 @@ struct erofs_super_block {
* 4~7 - reserved * 4~7 - reserved
*/ */
enum { enum {
EROFS_INODE_FLAT_PLAIN, EROFS_INODE_FLAT_PLAIN = 0,
EROFS_INODE_FLAT_COMPRESSION_LEGACY, EROFS_INODE_FLAT_COMPRESSION_LEGACY = 1,
EROFS_INODE_FLAT_INLINE, EROFS_INODE_FLAT_INLINE = 2,
EROFS_INODE_FLAT_COMPRESSION, EROFS_INODE_FLAT_COMPRESSION = 3,
EROFS_INODE_LAYOUT_MAX EROFS_INODE_LAYOUT_MAX
}; };
@ -184,7 +184,7 @@ struct erofs_xattr_entry {
/* available compression algorithm types */ /* available compression algorithm types */
enum { enum {
Z_EROFS_COMPRESSION_LZ4, Z_EROFS_COMPRESSION_LZ4 = 0,
Z_EROFS_COMPRESSION_MAX Z_EROFS_COMPRESSION_MAX
}; };
@ -242,10 +242,10 @@ struct z_erofs_map_header {
* (di_advise could be 0, 1 or 2) * (di_advise could be 0, 1 or 2)
*/ */
enum { enum {
Z_EROFS_VLE_CLUSTER_TYPE_PLAIN, Z_EROFS_VLE_CLUSTER_TYPE_PLAIN = 0,
Z_EROFS_VLE_CLUSTER_TYPE_HEAD, Z_EROFS_VLE_CLUSTER_TYPE_HEAD = 1,
Z_EROFS_VLE_CLUSTER_TYPE_NONHEAD, Z_EROFS_VLE_CLUSTER_TYPE_NONHEAD = 2,
Z_EROFS_VLE_CLUSTER_TYPE_RESERVED, Z_EROFS_VLE_CLUSTER_TYPE_RESERVED = 3,
Z_EROFS_VLE_CLUSTER_TYPE_MAX Z_EROFS_VLE_CLUSTER_TYPE_MAX
}; };