From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Sam Edwards <cfsworks@gmail.com>,
Yifan Zhao <zhaoyifan@sjtu.edu.cn>,
u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Cc: jnhuang95@gmail.com
Subject: Re: [PATCH] fs/erofs: Introduce new features including ztailpacking, fragments and dedupe
Date: Wed, 26 Jul 2023 09:23:48 +0800 [thread overview]
Message-ID: <0257005d-015c-96f7-eae4-aa19ff999332@linux.alibaba.com> (raw)
In-Reply-To: <5b20580e-f558-859f-6c63-20b11559a2cd@gmail.com>
Hi Sam,
On 2023/7/26 05:40, Sam Edwards wrote:
> Hi folks,
>
> On 7/7/23 09:52, Yifan Zhao wrote:
>> diff --git a/fs/erofs/internal.h b/fs/erofs/internal.h
>> index 4af7c91560..433a3c6c1e 100644
>> --- a/fs/erofs/internal.h
>> +++ b/fs/erofs/internal.h
>> +/* make sure that any user of the erofs headers has at least 64bit off_t type */
>> +extern int erofs_assert_largefile[sizeof(off_t) - 8];
>
> This assertion does not hold true on 32-bit platforms, and as a result this patch prevents building U-Boot on those systems with EROFS support enabled. Did you perhaps mean to use `erofs_off_t` (which is always 64-bit) somewhere that you're using `off_t` instead?
>
> I have had to revert this patch on my target, pending a solution for 32-bit users.
Thanks for your report.
I think this line could just be removed since it only impacts
LFS APIs ["erofs-utils which uses _FILE_OFFSET_BITS=64"] directly:
https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/commit/?id=8b88487e20a8fb79942793d2bd8fe9bd2b15ba62
https://lore.kernel.org/all/20221215085842.130804-1-raj.khem@gmail.com/
But EROFS userspace internal implementation doesn't use off_t directly
(instead it uses erofs_off_t as you said) nor u-boot interfaces (I think).
Yifan,
Could you submit a patch to remove this line?
Thanks,
Gao Xiang
>
> Thanks,
> Sam
prev parent reply other threads:[~2023-07-26 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 15:52 [PATCH] fs/erofs: Introduce new features including ztailpacking, fragments and dedupe Yifan Zhao
2023-07-11 3:12 ` Huang Jianan
2023-07-17 5:27 ` Gao Xiang
2023-07-17 15:12 ` Tom Rini
2023-07-17 15:26 ` Gao Xiang
2023-07-18 13:58 ` Tom Rini
2023-07-25 21:40 ` Sam Edwards
2023-07-26 1:23 ` Gao Xiang [this message]
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=0257005d-015c-96f7-eae4-aa19ff999332@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=cfsworks@gmail.com \
--cc=jnhuang95@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=zhaoyifan@sjtu.edu.cn \
/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