From: Gao Xiang <hsiangkao@redhat.com>
To: Yue Hu <zbestahu@gmail.com>
Cc: huyue2@yulong.com, linux-erofs <linux-erofs@lists.ozlabs.org>
Subject: Re: About Segmentation fault of mkfs.erofs in AOSP
Date: Tue, 1 Dec 2020 19:42:53 +0800 [thread overview]
Message-ID: <20201201114253.GA1323470@xiangao.remote.csb> (raw)
In-Reply-To: <20201201192309.00007531.zbestahu@gmail.com>
Hi Yue,
On Tue, Dec 01, 2020 at 07:23:09PM +0800, Yue Hu wrote:
> hi guys,
>
> I'm trying using erofs for super.img(dynamic partition) under Android 10. But i have met an issue below when building images:
>
> ```log
> EROFS: write_uncompressed_block() Line[140] Writing 3517 uncompressed data to block 63950
> EROFS: erofs_mkfs_build_tree() Line[1011] add file /tmp/merge_target_files_jnIVhM/output/VENDOR/etc/xtwifi.conf (nid 8185600, type 1)
> EROFS: erofs_mkfs_build_tree() Line[1011] add file /tmp/merge_target_files_jnIVhM/output/VENDOR/etc (nid 1790208, type 2)
> out/host/linux-x86/bin/mkerofsimage.sh: line 79: 188014 Segmentation fault (core dumped) $MAKE_EROFS_CMD
> ```
>
> Have you met this kind of issue? I'm trying to debug the problem, looks like memory related.
>
> BTW: i'm using latest erofs-utils in AOSP master branch (https://android.googlesource.com/platform/external/erofs-utils/).
Which lz4 version is used? it would be better to use lz4 1.9.3
(or 1.9.2 with some unexpected CR issues.)
For more details, please see README.
If the expected lz4 version is used, could you kindly leave gdb
backtrace message here as well?
Thanks,
Gao Xiang
>
> Thx.
>
next prev parent reply other threads:[~2020-12-01 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:23 About Segmentation fault of mkfs.erofs in AOSP Yue Hu
2020-12-01 11:42 ` Gao Xiang [this message]
2020-12-01 11:48 ` Yue Hu
2020-12-01 11:51 ` Gao Xiang
2020-12-02 9:59 ` Yue Hu
2020-12-02 10:41 ` Gao Xiang
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=20201201114253.GA1323470@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=huyue2@yulong.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=zbestahu@gmail.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