From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>, 53696@debbugs.gnu.org
Subject: bug#53696: Integer overflow on Guix GC size calculation
Date: Tue, 01 Feb 2022 22:20:18 +0100 [thread overview]
Message-ID: <a4c782cea72bf0ccb82f235ea76ce1a402a1aa59.camel@gmail.com> (raw)
In-Reply-To: <ZbUG0J0t7mjKPrXaPwoPrhN-Qx-jMae7vM2CCoOV-kHm7ID85ZoiNij86PcR8_zB2O9-DyxIPwWNlvCTS8AYSYemIuGJ4L8nNYwK0AXYuvQ=@elenq.tech>
Am Dienstag, dem 01.02.2022 um 14:06 +0000 schrieb Ekaitz Zarraga:
> Hi,
>
> I noticed there's some kind of a wierd integer overflow on the size
> calculation on `guix gc`:
>
> [17592186042896 MiB] deleting
> '/gnu/store/j2s6kva8l20m6rjj10bnknq99jc9rg6w-ghc-random-1.2.0-
> builder'
> [17592186042896 MiB] deleting
> '/gnu/store/8nx7zzj629qvv1533c48bl19wrkwcjh2-curl-7.79.1-doc'
> [17592186042897 MiB] deleting
> '/gnu/store/dcsi13588yyjws76s1wjc7h5spnjd2vn-ghc-kan-extensions-
> 5.2.3-builder'
> [17592186042897 MiB] deleting
> '/gnu/store/5zrhw6kvb8wd3n6lazpblqzsg92y320b-ghc-sop-core-0.5.0.1-
> builder'
> [17592186042897 MiB] deleting
> '/gnu/store/l2ya1z3la9qfdj9139f09q3djs36lw3l-ghc-aeson-pretty-0.8.9-
> builder'
> [17592186042897 MiB] deleting
> '/gnu/store/8a8nbfxq508r7qywkhaw8jj8hicpfjh8-ghc-prelude-extras-
> 0.4.0.3-builder'
> [17592186042897 MiB] deleting
> '/gnu/store/wbz6vkiz7cq8c531xvb31lxm28nz332i-ghc-8.10.7'
> [19 MiB] deleting '/gnu/store/i5np7ifiabg333g2l8ycmvbhimnrrx8k-ghc-
> 8.10.7-doc'
> [170 MiB] deleting '/gnu/store/yx9zjw9118gzfcx33adfwy6kghrzxkys-ghc-
> pem-0.2.4-builder'
> [170 MiB] deleting '/gnu/store/pinvkg1x5rpsgm95zhn50l6xq7rly43f-perl-
> test-output-1.033.drv'
> [170 MiB] deleting '/gnu/store/k1bdc950d62g1pw4yw1khgmfr32m3rpm-perl-
> sub-exporter-0.988.drv'
I find it somewhat concerning that you've accumulated more than 2^64
bytes of garbage. Are some items counted double here?
Other than that, that's pretty normal size_t wraparound semantics. I
don't think that number is used for anything other than displaying.
Cheers
next prev parent reply other threads:[~2022-02-02 2:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 14:06 bug#53696: Integer overflow on Guix GC size calculation Ekaitz Zarraga
2022-02-01 21:20 ` Liliana Marie Prikler [this message]
2022-02-01 21:54 ` Ekaitz Zarraga
2022-02-02 19:45 ` Liliana Marie Prikler
2022-02-02 19:51 ` Ekaitz Zarraga
2022-02-02 20:04 ` Liliana Marie Prikler
2022-02-02 10:05 ` Maxime Devos
2022-02-02 12:04 ` Bengt Richter
2022-02-02 22:46 ` Bengt Richter
2022-02-08 10:01 ` Ludovic Courtès
2022-02-08 10:52 ` Ekaitz Zarraga
2022-02-10 20:25 ` Ludovic Courtès
2022-02-10 20:27 ` Ekaitz Zarraga
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=a4c782cea72bf0ccb82f235ea76ce1a402a1aa59.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=53696@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
/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).