From: Willy Tarreau <w@1wt.eu>
To: Daniel Palmer <daniel@thingy.jp>
Cc: linux@weissschuh.net, david.laight.linux@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] nolibc: Add fallocate()
Date: Mon, 11 May 2026 08:29:32 +0200 [thread overview]
Message-ID: <agF3TNFzf_HS49rj@1wt.eu> (raw)
In-Reply-To: <20260507090353.356764-1-daniel@thingy.jp>
Hi Daniel,
On Thu, May 07, 2026 at 06:03:50PM +0900, Daniel Palmer wrote:
> While poking around with my "static PIE for nommu" series I found
> I needed fallocate(). Implementing it turned out a bit more
> interesting than I thought it would be due to how the offset and
> size need to be passed on 32bit machines.
>
> v4:
> - Added statfs()...
> - Reworked the test a bit to use statfs() to work out if /tmp
> is a tmpfs or not and skip the test if it isn't. This skips
> the test on sparc32 where CONFIG_TMPFS=n.
> - Adding the needed bits to the sparc32 config to allow tmpfs
> to be enabled allows it to run and pass the test. I will check
> the changes and send a patch.
> - Cleaned up the if() around deciding how to pass the parameters
> for fallocate() based on the comments from David and Thomas.
> - Test passed on all of the supported targets.
(...)
Thanks, the whole series looks good to me:
Acked-by: Willy Tarreau <w@1wt.eu>
Let's wait for Thomas who usually spots finer issues than me ;-)
Thanks,
Willy
prev parent reply other threads:[~2026-05-11 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 9:03 [PATCH v4 0/3] nolibc: Add fallocate() Daniel Palmer
2026-05-07 9:03 ` [PATCH v4 1/3] tools/nolibc: fcntl: " Daniel Palmer
2026-05-07 9:03 ` [PATCH v4 2/3] tools/nolibc: Add statfs() Daniel Palmer
2026-05-07 9:03 ` [PATCH v4 3/3] selftests/nolibc: Add a very basic test for fallocate() Daniel Palmer
2026-05-11 6:29 ` Willy Tarreau [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=agF3TNFzf_HS49rj@1wt.eu \
--to=w@1wt.eu \
--cc=daniel@thingy.jp \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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