From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Cc: "xiuhong.wang" <xiuhong.wang@unisoc.com>,
Zhiguo Niu <zhiguo.niu@unisoc.com>
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs-tools: Build f2fs-tools with _FILE_OFFSET_BITS=64
Date: Thu, 2 Jul 2026 15:31:03 +0800 [thread overview]
Message-ID: <e241092f-1634-47d3-befd-00fbd4a65706@kernel.org> (raw)
In-Reply-To: <20260702065602.4120914-1-jaegeuk@kernel.org>
On 7/2/26 14:56, Jaegeuk Kim via Linux-f2fs-devel wrote:
> From: "xiuhong.wang" <xiuhong.wang@unisoc.com>
>
> After commit b15b6cc56ac7("f2fs-tools: convert to lseek() and kill
> lseek64"), 32-bit Android should also be built with
> _FILE_OFFSET_BITS=64.
>
> When calling the lseek function on arm32, if the offset exceeds 32
> bits, lseek fails. Therefore, the flag _FILE_OFFSET_BITS=64 is
> added to support operations with offsets greater than 32 bits on
> arm32.
>
> Signed-off-by: Xiuhong Wang <xiuhong.wang@unisoc.com>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-07-02 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:56 [f2fs-dev] [PATCH 1/3] f2fs-tools: Build f2fs-tools with _FILE_OFFSET_BITS=64 Jaegeuk Kim via Linux-f2fs-devel
2026-07-02 6:56 ` [f2fs-dev] [PATCH 2/3] f2fs_io: add include dir Jaegeuk Kim via Linux-f2fs-devel
2026-07-02 7:31 ` Chao Yu via Linux-f2fs-devel
2026-07-02 6:56 ` [f2fs-dev] [PATCH 3/3] f2fs-tools: fix build failure on mac Jaegeuk Kim via Linux-f2fs-devel
2026-07-02 7:31 ` Chao Yu via Linux-f2fs-devel
2026-07-02 7:31 ` Chao Yu via Linux-f2fs-devel [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=e241092f-1634-47d3-befd-00fbd4a65706@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=xiuhong.wang@unisoc.com \
--cc=zhiguo.niu@unisoc.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.