From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: ludo@gnu.org, 70877@debbugs.gnu.org
Subject: bug#70877: guix-daemon fails to copy 4+GB file to store
Date: Sun, 12 May 2024 10:12:11 +0300 [thread overview]
Message-ID: <ZkBrywRMBFbtlZqU@3900XT> (raw)
In-Reply-To: <87msowpqm2.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
On Sat, May 11, 2024 at 12:52:53PM +0200, Ricardo Wurmus wrote:
> The guix-daemon's libutil/util.cc uses copy_file_range to copy a
> downloaded file into the store. copy_file_range fails on files larger
> than 4GB with an error like this:
>
> guix build: error: short write in copy_file_range `15' to `16': No such file or directory
>
> The man page for copy_file_range says that it could return EFBIG when
> the range exceeds the maximum range. The daemon code does not check any
> limits and will attempt to copy the whole file.
>
> I believe our code ought to check the value of st.size and fall back to
> a boring copy if it exceeds some "reasonable" value.
>
> This is where copy_file_range is used:
> https://git.savannah.gnu.org/cgit/guix.git/tree/nix/libutil/util.cc#n382
>
> Here is a little reproducer:
>
> (use-modules (guix download)
> (guix packages)
> (guix build-system trivial))
>
> (package
> (name "chungus")
> (version "1")
> (source
> (origin
> (method url-fetch)
> (uri "http://localhost:1111/chungus")
> (sha256
> (base32 "0nx67d4ls2nfwcfdmg81vf240z6lpwpdqypssr1wzn3hyz4szci4"))))
> (build-system trivial-build-system)
> (home-page "")
> (synopsis "")
> (description "")
> (license #f))
>
> --8<---------------cut here---------------start------------->8---
> # generate a big file
> dd bs=1M count=4096 if=/dev/zero of=/tmp/chungus
> # serve it
> guix shell woof -- woof -i 127.0.0.1 -p 1111 -c 1 /tmp/chungus
> # build the source derivation
> guix build --no-grafts -Sf bug.scm
> # observe the error
> # guix build: error: short write in copy_file_range `15' to `16': No such file or directory
> --8<---------------cut here---------------end--------------->8---
>
This sounds like a similar failure to bug 65714 that I ran into with
guix copy, but I wasn't able to diagnose it.
https://issues.guix.gnu.org/65714
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-12 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 10:52 bug#70877: guix-daemon fails to copy 4+GB file to store Ricardo Wurmus
2024-05-12 7:12 ` Efraim Flashner [this message]
2024-05-13 10:10 ` Ludovic Courtès
2024-05-13 12:09 ` Ricardo Wurmus
2024-05-13 14:34 ` Ludovic Courtès
2024-05-13 16:24 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZkBrywRMBFbtlZqU@3900XT \
--to=efraim@flashner.co.il \
--cc=70877@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).