All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li GuiFu via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Gao Xiang <hsiangkao@aol.com>, linux-erofs@lists.ozlabs.org
Cc: Guo Weichao <guoweichao@oppo.com>
Subject: Re: [PATCH 1/3] erofs-utils: introduce fuse implementation
Date: Sun, 22 Nov 2020 12:43:31 +0800	[thread overview]
Message-ID: <8c768a92-3126-006c-1272-8c8022e8c792@aliyun.com> (raw)
In-Reply-To: <20201120174146.18662-2-hsiangkao@aol.com>

Gao Xiang

It run good, some codes format need to be adjusted
Please re-send to make more readable

On 2020/11/21 1:41, Gao Xiang via Linux-erofs wrote:
> From: Li Guifu <blucerlee@gmail.com>
> 
> Let's add a simple erofsfuse approach, and benefits are:
> 
>  - images can be supported on various platforms;
>  - new unpack tool can be developed based on this;
>  - new on-disk features can be iterated, verified effectively.
> 
> This commit only addresses reading uncompressed regular files.
> Other file (e.g. compressed file) support is out of scope here.
> 
> Note that erofsfuse is an unstable feature for now (also notice
> LZ4_decompress_safe_partial() was broken in lz4-1.9.2, which
> just fixed in lz4-1.9.3), let's disable it by default for a while.
> 
> Signed-off-by: Li Guifu <blucerlee@gmail.com>
> Signed-off-by: Huang Jianan <huangjianan@oppo.com>
> Signed-off-by: Guo Weichao <guoweichao@oppo.com>
> Signed-off-by: Gao Xiang <hsiangkao@aol.com>
> ---

> +
> +static void signal_handle_sigsegv(int signal)
> +{
> +	void *array[10];
> +	size_t nptrs;
> +	char **strings;
> +	size_t i;
> +
> +	erofs_dump("========================================\n");
> +	erofs_dump("Segmentation Fault.  Starting backtrace:\n");
> +	nptrs = backtrace(array, 10);
> +	strings = backtrace_symbols(array, nptrs);
> +	if (strings) {
> +		for (i = 0; i < nptrs; i++)
> +			erofs_dbg("%s", strings[i]);

erofs_dbg change to erofs_dump to make all log printed, "\n" is needed

> +		free(strings);
> +	}
> +	erofs_dump("========================================\n");
> +	abort();
> +}
> +
> +

>  
> +static inline unsigned int erofs_bitrange(unsigned int value, unsigned int bit,
> +					  unsigned int bits)
> +{
> +
empty line is not needed

> +	return (value >> bit) & ((1 << bits) - 1);
> +}
> +
> +
empty line is not needed
> +static inline unsigned int erofs_inode_version(unsigned int value)
> +{
> +	return erofs_bitrange(value, EROFS_I_VERSION_BIT,
> +			      EROFS_I_VERSION_BITS);
> +}
> +
> +static inline unsigned int erofs_inode_datalayout(unsigned int value)
> +{
> +	return erofs_bitrange(value, EROFS_I_DATALAYOUT_BIT,
> +			      EROFS_I_DATALAYOUT_BITS);
> +}
> +

  reply	other threads:[~2020-11-22  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201120174146.18662-1-hsiangkao.ref@aol.com>
2020-11-20 17:41 ` [PATCH 0/3] erofs-utils: introduce fuse implementation Gao Xiang via Linux-erofs
2020-11-20 17:41   ` [PATCH 1/3] " Gao Xiang via Linux-erofs
2020-11-22  4:43     ` Li GuiFu via Linux-erofs [this message]
2020-11-22  4:58       ` Gao Xiang
2020-11-20 17:41   ` [PATCH 2/3] erofs-utils: fuse: support symlink & special inode Gao Xiang via Linux-erofs
2020-11-20 17:41   ` [PATCH 3/3] erofs-utils: fuse: add compressed file support 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=8c768a92-3126-006c-1272-8c8022e8c792@aliyun.com \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=bluce.lee@aliyun.com \
    --cc=guoweichao@oppo.com \
    --cc=hsiangkao@aol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.