From: Gao Xiang <gaoxiang25@huawei.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<devel@driverdev.osuosl.org>, LKML <linux-kernel@vger.kernel.org>,
<linux-erofs@lists.ozlabs.org>, Chao Yu <chao@kernel.org>,
Miao Xie <miaoxie@huawei.com>, <weidu.du@huawei.com>,
Fang Wei <fangwei1@huawei.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] staging: erofs: add requirements field in superblock
Date: Tue, 11 Jun 2019 09:43:36 +0800 [thread overview]
Message-ID: <6993c266-0c95-780f-56b2-97996ee3be73@huawei.com> (raw)
In-Reply-To: <f4fbd407-7f0d-bbe3-2283-f7291a29026a@huawei.com>
Hi Chao,
On 2019/6/11 9:37, Chao Yu wrote:
> On 2019/6/10 17:36, Gao Xiang wrote:
>> There are some backward incompatible optimizations pending
>> for months, mainly due to on-disk format expensions.
>>
>> However, we should ensure that it cannot be mounted with
>> old kernels. Otherwise, it will causes unexpected behaviors.
>>
>> Fixes: ba2b77a82022 ("staging: erofs: add super block operations")
>> Cc: <stable@vger.kernel.org> # 4.19+
>> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
>> ---
>> drivers/staging/erofs/erofs_fs.h | 11 +++++++++--
>> drivers/staging/erofs/super.c | 8 ++++++++
>> 2 files changed, 17 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/staging/erofs/erofs_fs.h b/drivers/staging/erofs/erofs_fs.h
>> index fa52898df006..531821757845 100644
>> --- a/drivers/staging/erofs/erofs_fs.h
>> +++ b/drivers/staging/erofs/erofs_fs.h
>> @@ -17,10 +17,16 @@
>> #define EROFS_SUPER_MAGIC_V1 0xE0F5E1E2
>> #define EROFS_SUPER_OFFSET 1024
>>
>> +/*
>> + * Any bits that aren't in EROFS_ALL_REQUIREMENTS should be
>> + * incompatible with this kernel version.
>> + */
>> +#define EROFS_ALL_REQUIREMENTS 0
>> +
>> struct erofs_super_block {
>> /* 0 */__le32 magic; /* in the little endian */
>> /* 4 */__le32 checksum; /* crc32c(super_block) */
>> -/* 8 */__le32 features;
>> +/* 8 */__le32 features; /* extra features for the image */
>> /* 12 */__u8 blkszbits; /* support block_size == PAGE_SIZE only */
>> /* 13 */__u8 reserved;
>>
>> @@ -34,8 +40,9 @@ struct erofs_super_block {
>> /* 44 */__le32 xattr_blkaddr;
>> /* 48 */__u8 uuid[16]; /* 128-bit uuid for volume */
>> /* 64 */__u8 volume_name[16]; /* volume name */
>> +/* 80 */__le32 requirements; /* all mandatory minimum requirements */
>>
>> -/* 80 */__u8 reserved2[48]; /* 128 bytes */
>> +/* 84 */__u8 reserved2[44]; /* 128 bytes */
>
> Xiang,
>
> It needs to update the comment behind reserved2, it's locating at 132 bytes.
I don't get the point... the whole struct is totally 128bytes I think?
>
>> } __packed;
>>
>> /*
>> diff --git a/drivers/staging/erofs/super.c b/drivers/staging/erofs/super.c
>> index f580d4ef77a1..815e5825db59 100644
>> --- a/drivers/staging/erofs/super.c
>> +++ b/drivers/staging/erofs/super.c
>> @@ -104,6 +104,14 @@ static int superblock_read(struct super_block *sb)
>> goto out;
>> }
>>
>> + /* check if the kernel meets all mandatory requirements */
>> + if (le32_to_cpu(layout->requirements) & (~EROFS_ALL_REQUIREMENTS)) {
>> + errln("too old to meet minimum requirements: %x supported: %x",
>
> It will be better to give a suggestion to user to upgrade kernel version to
> match the image with new layout, otherwise it's just a little confused about
> above printed message.
OK, I will refine the printed message :)
Thanks,
Gao Xiang
>
> Thanks,
>
>> + le32_to_cpu(layout->requirements),
>> + EROFS_ALL_REQUIREMENTS);
>> + goto out;
>> + }
>> +
>> sbi->blocks = le32_to_cpu(layout->blocks);
>> sbi->meta_blkaddr = le32_to_cpu(layout->meta_blkaddr);
>> #ifdef CONFIG_EROFS_FS_XATTR
>>
next prev parent reply other threads:[~2019-06-11 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 9:36 Gao Xiang
2019-06-10 9:36 ` [PATCH 2/2] staging: erofs: rename data_mapping_mode to datamode Gao Xiang
2019-06-11 1:39 ` Chao Yu
2019-06-11 1:37 ` [PATCH 1/2] staging: erofs: add requirements field in superblock Chao Yu
2019-06-11 1:43 ` Gao Xiang [this message]
2019-06-11 1:47 ` Chao Yu
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=6993c266-0c95-780f-56b2-97996ee3be73@huawei.com \
--to=gaoxiang25@huawei.com \
--cc=chao@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=fangwei1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=stable@vger.kernel.org \
--cc=weidu.du@huawei.com \
--cc=yuchao0@huawei.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 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®