From: Lucas Karpinski <lkarpinski@nvidia.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>,
"zhaoyifan (H)" <zhaoyifan28@huawei.com>,
linux-erofs@lists.ozlabs.org
Cc: jcalmels@nvidia.com
Subject: Re: [PATCH v3 3/4] erofs-utils: mfks: add rebuild FULLDATA for combined EROFS images
Date: Wed, 15 Apr 2026 09:30:50 -0400 [thread overview]
Message-ID: <1199c33b-9015-4ac9-ac2a-198f7235f8ff@nvidia.com> (raw)
In-Reply-To: <cc8eda08-ba1d-4c0c-b4df-16ebc65dcbea@linux.alibaba.com>
On 2026-04-15 3:47 a.m., Gao Xiang wrote:
>
>
> On 2026/4/15 11:35, zhaoyifan (H) wrote:
>> This patch incorrectly handles inline inode:
>>
>> Reproduce in erofs-utils directory:
>> mkfs/mkfs.erofs 1.erofs man/
>> mkfs/mkfs.erofs 2.erofs docs/
>> mkfs/mkfs.erofs --clean=data merged.erofs 1.erofs 2.erofs
>>
>> Then PERFORMANCE.md in merged.erofs contains incorrect data after
>> offset 0x2000.
>>
>> Fixed with following diff:
>>
>> diff --git a/lib/inode.c b/lib/inode.c
>> index bd10e26..36dce56 100644
>> --- a/lib/inode.c
>> +++ b/lib/inode.c
>> @@ -683,6 +683,13 @@ static int erofs_write_unencoded_data(struct
>> erofs_inode *inode,
>>
>> /* read the tail-end data */
>> if (inode->idata_size) {
>> + /*
>> + * If inode->idata is already present, the caller has
>> prepared
>> + * the tail data and nothing more needs to be done here.
>> + */
>> + if (inode->idata)
>> + return 0;
>
> Yes, it should be fixed as:
> /*
> * Read the tail-end data if inode->idata is NULL; if the tail data
> * has been prepared then nothing more needs to be done here.
> */
> if (inode->idata_size && !inode->idata) {
> }
>
> ...
>
>>> +#include "liberofs_cache.h"
>> Unnecessary include `liberofs_cache.h`
>
> That would be nice to be addressed too.
>
>
> I've applied [PATCH 1 and 2], could you send v4 to address this?
>
> Thanks,
> Gao Xiang
Thanks for the catch Zhao and ACK will add the changes.
next prev parent reply other threads:[~2026-04-15 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 19:10 [PATCH v3 0/4] erofs-utils: implement the FULLDATA rebuild mode Lucas Karpinski
2026-04-14 19:10 ` [PATCH v3 1/4] erofs-utils: lib: remove redundant if check Lucas Karpinski
2026-04-14 19:10 ` [PATCH v3 2/4] erofs-utils: lib: add helper function erofs_uuid_unparse_as_tag Lucas Karpinski
2026-04-14 19:10 ` [PATCH v3 3/4] erofs-utils: mfks: add rebuild FULLDATA for combined EROFS images Lucas Karpinski
2026-04-15 3:35 ` zhaoyifan (H)
2026-04-15 7:47 ` Gao Xiang
2026-04-15 13:30 ` Lucas Karpinski [this message]
2026-04-14 19:10 ` [PATCH v3 4/4] erofs-utils: manpages: update to reflect fulldata support Lucas Karpinski
2026-04-15 2:07 ` [PATCH v3 0/4] erofs-utils: implement the FULLDATA rebuild mode Gao Xiang
2026-04-15 14:09 ` Lucas Karpinski
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=1199c33b-9015-4ac9-ac2a-198f7235f8ff@nvidia.com \
--to=lkarpinski@nvidia.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jcalmels@nvidia.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=zhaoyifan28@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