From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Jia Zhu <zhujia.zj@bytedance.com>,
xiang@kernel.org, chao@kernel.org, gerry@linux.alibaba.com,
linux-erofs@lists.ozlabs.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jefflexu@linux.alibaba.com, huyue2@coolpad.com,
Xin Yin <yinxin.x@bytedance.com>
Subject: Re: [PATCH] erofs: support for mounting a single block device with multiple devices
Date: Wed, 1 Mar 2023 15:08:48 +0800 [thread overview]
Message-ID: <c3c10f27-7941-6ccc-fa60-b5a289bf03ba@linux.alibaba.com> (raw)
In-Reply-To: <20230301070417.13084-1-zhujia.zj@bytedance.com>
Hi Jia,
On 2023/3/1 15:04, Jia Zhu wrote:
> In order to support mounting multi-layer container image as a block
> device, add single block device with multiple devices feature for EROFS.
In order to support mounting multi-blob container image as a single
flattened block device, add flattened block device feature for EROFS.
>
> In this mode, all meta/data contents will be mapped into one block address.
> User could directly mount the block device by EROFS.
>
> Signed-off-by: Jia Zhu <zhujia.zj@bytedance.com>
> Reviewed-by: Xin Yin <yinxin.x@bytedance.com>
> ---
> fs/erofs/data.c | 8 ++++++--
> fs/erofs/super.c | 5 +++++
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/fs/erofs/data.c b/fs/erofs/data.c
> index e16545849ea7..870b1f7fe1d4 100644
> --- a/fs/erofs/data.c
> +++ b/fs/erofs/data.c
> @@ -195,9 +195,9 @@ int erofs_map_dev(struct super_block *sb, struct erofs_map_dev *map)
> {
> struct erofs_dev_context *devs = EROFS_SB(sb)->devs;
> struct erofs_device_info *dif;
> + bool flatdev = !!sb->s_bdev;
I'd like to land it in sbi and set it in advance?
Also, did you test this patch?
Thanks,
Gao Xiang
> int id;
>
> - /* primary device by default */
> map->m_bdev = sb->s_bdev;
> map->m_daxdev = EROFS_SB(sb)->dax_dev;
> map->m_dax_part_off = EROFS_SB(sb)->dax_part_off;
> @@ -210,12 +210,16 @@ int erofs_map_dev(struct super_block *sb, struct erofs_map_dev *map)
> up_read(&devs->rwsem);
> return -ENODEV;
> }
> + if (flatdev) {
> + map->m_pa += blknr_to_addr(dif->mapped_blkaddr);
> + map->m_deviceid = 0;
> + }
> map->m_bdev = dif->bdev;
> map->m_daxdev = dif->dax_dev;
> map->m_dax_part_off = dif->dax_part_off;
> map->m_fscache = dif->fscache;
> up_read(&devs->rwsem);
> - } else if (devs->extra_devices) {
> + } else if (devs->extra_devices && !flatdev) {
> down_read(&devs->rwsem);
> idr_for_each_entry(&devs->tree, dif, id) {
> erofs_off_t startoff, length;
> diff --git a/fs/erofs/super.c b/fs/erofs/super.c
> index 19b1ae79cec4..4f9725b0950c 100644
> --- a/fs/erofs/super.c
> +++ b/fs/erofs/super.c
> @@ -226,6 +226,7 @@ static int erofs_init_device(struct erofs_buf *buf, struct super_block *sb,
> struct erofs_fscache *fscache;
> struct erofs_deviceslot *dis;
> struct block_device *bdev;
> + bool flatdev = !!sb->s_bdev;
> void *ptr;
>
> ptr = erofs_read_metabuf(buf, sb, erofs_blknr(*pos), EROFS_KMAP);
> @@ -248,6 +249,10 @@ static int erofs_init_device(struct erofs_buf *buf, struct super_block *sb,
> if (IS_ERR(fscache))
> return PTR_ERR(fscache);
> dif->fscache = fscache;
> + } else if (flatdev) {
> + dif->bdev = sb->s_bdev;
> + dif->dax_dev = EROFS_SB(sb)->dax_dev;
> + dif->dax_part_off = sbi->dax_part_off;
> } else {
> bdev = blkdev_get_by_path(dif->path, FMODE_READ | FMODE_EXCL,
> sb->s_type);
next prev parent reply other threads:[~2023-03-01 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 7:04 [PATCH] erofs: support for mounting a single block device with multiple devices Jia Zhu
2023-03-01 7:08 ` Gao Xiang [this message]
2023-03-01 7:44 ` Jia Zhu
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=c3c10f27-7941-6ccc-fa60-b5a289bf03ba@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=gerry@linux.alibaba.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=yinxin.x@bytedance.com \
--cc=zhujia.zj@bytedance.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;
as well as URLs for NNTP newsgroup(s).