From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: linux-erofs@lists.ozlabs.org
Cc: Zhang Shiming <zhangshiming@oppo.com>, Guo Weichao <guoweichao@oppo.com>
Subject: [WIP] [PATCH 00/12] erofs-utils: introduce fuse implementation
Date: Sat, 17 Oct 2020 13:16:09 +0800 [thread overview]
Message-ID: <20201017051621.7810-1-hsiangkao@aol.com> (raw)
In-Reply-To: 20201017051621.7810-1-hsiangkao.ref@aol.com
Hi all,
This patchset is based on the original patch
https://lore.kernel.org/r/20190818135923.27444-1-blucerlee@gmail.com
and several fixes / compression support by Huang Jianan
https://lore.kernel.org/r/20201015133959.61007-1-huangjianan@oppo.com
with my additional 9 incremental patches to refactor my current
development status, which will be folded into original patches
in the next WIP version since the fuse approach hasn't been
merged into dev branch yet.
To summarize the benefits of erofsfuse, I think it would be:
- erofs images can be supported on various platforms;
- an independent unpack tool can be developed based on this;
- new on-disk feature can be iterated, verified effectively.
Any feedback or/and follow-on development/cleanup is welcomed.
(we still have a lot to do for the entire erofsfuse codebase...)
Thanks,
Gao Xiang
Gao Xiang (9):
erofs-utils: fuse: adjust larger extent handling
erofs-utils: fuse: use proper expression about inode size
erofs-utils: fuse: drop ofs_out
erofs-utils: fuse: refuse a undefined shifted cluster behavior
erofs-utils: fuse: drop z_erofs_shifted_transform()
erofs-utils: fuse: rename ofs_head and outputsize
erofs-utils: fuse: cleanup erofs_read_data_compression()
erofs-utils: fuse: move up mpage in struct erofs_map_blocks
erofs-utils: fuse: fix up source headers
Huang Jianan (2):
erofs-utils: fuse: support read special file
erofs-utils: fuse: support read compressed file
Li Guifu (1):
erofs-utils: introduce fuse implementation
Makefile.am | 2 +-
README | 28 ++-
configure.ac | 3 +-
fuse/Makefile.am | 18 ++
fuse/decompress.c | 84 ++++++++
fuse/decompress.h | 42 ++++
fuse/dentry.c | 129 ++++++++++++
fuse/dentry.h | 43 ++++
fuse/disk_io.c | 72 +++++++
fuse/disk_io.h | 21 ++
fuse/getattr.c | 65 ++++++
fuse/getattr.h | 15 ++
fuse/init.c | 118 +++++++++++
fuse/init.h | 24 +++
fuse/logging.c | 81 ++++++++
fuse/logging.h | 55 ++++++
fuse/main.c | 171 ++++++++++++++++
fuse/namei.c | 242 +++++++++++++++++++++++
fuse/namei.h | 22 +++
fuse/open.c | 22 +++
fuse/open.h | 15 ++
fuse/read.c | 214 ++++++++++++++++++++
fuse/read.h | 17 ++
fuse/readir.c | 123 ++++++++++++
fuse/readir.h | 17 ++
fuse/zmap.c | 417 +++++++++++++++++++++++++++++++++++++++
include/erofs/defs.h | 16 ++
include/erofs/internal.h | 79 ++++++++
include/erofs_fs.h | 4 +
29 files changed, 2156 insertions(+), 3 deletions(-)
create mode 100644 fuse/Makefile.am
create mode 100644 fuse/decompress.c
create mode 100644 fuse/decompress.h
create mode 100644 fuse/dentry.c
create mode 100644 fuse/dentry.h
create mode 100644 fuse/disk_io.c
create mode 100644 fuse/disk_io.h
create mode 100644 fuse/getattr.c
create mode 100644 fuse/getattr.h
create mode 100644 fuse/init.c
create mode 100644 fuse/init.h
create mode 100644 fuse/logging.c
create mode 100644 fuse/logging.h
create mode 100644 fuse/main.c
create mode 100644 fuse/namei.c
create mode 100644 fuse/namei.h
create mode 100644 fuse/open.c
create mode 100644 fuse/open.h
create mode 100644 fuse/read.c
create mode 100644 fuse/read.h
create mode 100644 fuse/readir.c
create mode 100644 fuse/readir.h
create mode 100644 fuse/zmap.c
--
2.24.0
next parent reply other threads:[~2020-10-17 5:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201017051621.7810-1-hsiangkao.ref@aol.com>
2020-10-17 5:16 ` Gao Xiang via Linux-erofs [this message]
2020-10-17 5:16 ` [WIP] [PATCH 01/12] erofs-utils: introduce fuse implementation Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 02/12] erofs-utils: fuse: support read special file Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 03/12] erofs-utils: fuse: support read compressed file Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 04/12] erofs-utils: fuse: adjust larger extent handling Gao Xiang via Linux-erofs
2020-10-19 3:13 ` 回复: " huangjianan
2020-10-19 3:32 ` Gao Xiang via Linux-erofs
2020-10-19 4:49 ` 回复: " Huang Jianan
2020-10-19 3:37 ` 回复: " Huang Jianan
2020-10-19 3:43 ` Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 05/12] erofs-utils: fuse: use proper expression about inode size Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 06/12] erofs-utils: fuse: drop ofs_out Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 07/12] erofs-utils: fuse: refuse a undefined shifted cluster behavior Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 08/12] erofs-utils: fuse: drop z_erofs_shifted_transform() Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 09/12] erofs-utils: fuse: rename ofs_head and outputsize Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 10/12] erofs-utils: fuse: cleanup erofs_read_data_compression() Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 11/12] erofs-utils: fuse: move up mpage in struct erofs_map_blocks Gao Xiang via Linux-erofs
2020-10-17 5:16 ` [WIP] [PATCH 12/12] erofs-utils: fuse: fix up source headers Gao Xiang via Linux-erofs
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=20201017051621.7810-1-hsiangkao@aol.com \
--to=linux-erofs@lists.ozlabs.org \
--cc=guoweichao@oppo.com \
--cc=hsiangkao@aol.com \
--cc=zhangshiming@oppo.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).