From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_LOW,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14598 invoked from network); 26 Jun 2023 19:36:23 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 26 Jun 2023 19:36:23 -0000 Received: (qmail 28151 invoked by uid 550); 26 Jun 2023 19:36:20 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 26521 invoked from network); 26 Jun 2023 19:34:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20221208; t=1687808078; x=1690400078; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=/AAaHEDSh2njePU+TruQvhfFLQKHVuWE3lNFvBTo/WQ=; b=Hb8Oco6y3dxocskGtlCTib9gmlgESM7VgTml8DUpe6dZTgUSucq6gxIaVScIqtwrxT 1HiG/d+7Cqk3V8+gL1DQ5F0gR7ftOW+AcW28LQikhn+nFUgG51H/bMhpKcDtiMyYML2l XJNMmLsAqEOL2YHavKePVC/tdBfDL0axPS8n9Qd33WIJV5mLFhCtE/zLjJZTnaJeC+da Ir5nLp4FLigeObOJoxd2+qm+XKO9nQ8YYzmdTFNwDQWbw1qFtrY2MMrVc7UEOH1Zr/O+ hHh4qZ1uS8NPhMz4Az0hEle30rqQPZ5+3E/E2YKULxnzEc9ehbKZgFU4+/8m7udSq8Cj 10/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687808078; x=1690400078; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=/AAaHEDSh2njePU+TruQvhfFLQKHVuWE3lNFvBTo/WQ=; b=SpACC5EaFgRl205N/lI1CEU1Zr9voBKdmLCiFjeD+gHlwoLrULgoqylrNRVrsVVxg/ 76r5u7UXgwE2Ho5bS5WjXQy+Uwj+JcGkJbS8cVeznMNGSw5dOyhtSCjHWggIXxbli0Xq 4rWg6DlHFf5RrsEWNRnm8YJvUUSFQ6gj+z/LYP+5hGWs1e53b32gzb3W/wBBdV5+74rZ spEifaRGuSyh92P3L3YEg/HZD2YfzopBqcFs/DBde0v7+JvLOk/K7d1nxzadMFCPWYHj baFg0JZxu6XHSBqS7d96ZMe1QNSDOJG/cFJtVLtdlfEhJvhfxwzk2bnWsv653AIhRkup dB4Q== X-Gm-Message-State: AC+VfDzAsr0rE9P307DbNDU8h3kHD/IELpjFmuhDGTLY9RtUEyKv3m6b 1ii8YOUE2PM5vsH+dC0kzFNEbwB3JrkbYOuGE050syi2CSg= X-Google-Smtp-Source: ACHHUZ7bNKhgY6pIMAowgy44gnxd29TwaNGF2Jxhw/PbViGH9xLrqqwZrxiJfQtZkljYHlci3JMgakZdxYTO3y0DIlM= X-Received: by 2002:a2e:9d16:0:b0:2b6:9e83:73da with SMTP id t22-20020a2e9d16000000b002b69e8373damr2418657lji.32.1687808078033; Mon, 26 Jun 2023 12:34:38 -0700 (PDT) MIME-Version: 1.0 From: Immolo Date: Mon, 26 Jun 2023 20:34:04 +0100 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="000000000000f0b63405ff0d709a" Subject: [musl] m68k - malloc causing 'out of memory: my_alloc caller' in rsync --000000000000f0b63405ff0d709a Content-Type: text/plain; charset="UTF-8" Hi, I've been testing using Gentoo on m68k with musl -1.2.4 over the last few days and hit an interesting issue when running `emerge --sync` to update the portage tree would cause the following error: [receiver] out of memory: my_alloc caller (file=flist.c, line=311) rsync error: error allocating core memory buffers (code 22) at util2.c(123) [receiver=3.2.7] [generator] out of memory: my_alloc caller (file=flist.c, line=311) rsync error: error allocating core memory buffers (code 22) at util2.c(123) [generator=3.2.7] rsync: [receiver] write error: Broken pipe (32) Full output here: https://bpa.st/3VDNM Looking at the source code of the files it highlights it seems to be an issue in the malloc: https://github.com/WayneD/rsync/blob/master/util2.c#L123 https://github.com/WayneD/rsync/blob/master/flist.c#L311 https://github.com/WayneD/rsync/blob/master/fileio.c#L159 I've tested to see if a local rsync mirror will cause the same error with random files and found it happens at around 62 files being mirrored but size of the file does not matter. I run musll on multiple architectures and this is the first time I've run across it and have confirmed the Gentoo glibc m68k install does not run into this. --000000000000f0b63405ff0d709a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I've been testing us= ing Gentoo on m68k with musl -1.2.4 over the last few days and hit an inter= esting issue when running `emerge --sync` to update the portage tree would = cause the following error:

[receiver] out of mem= ory: my_alloc caller (file=3Dflist.c, line=3D311)
rsync error: error allocating c= ore memory buffers (code 22) at util2.c(123) [receiver=3D3.2.7]
[generator] out of memory: my_a= lloc caller (file=3Dflist.c, line=3D311)
rsync error: error allocating c= ore memory buffers (code 22) at util2.c(123) [generator=3D3.2.7]
rsync: [receiver] write error: = Broken pipe (32)
Full output here: https= ://bpa.st/3VDNM

Looking at the source code of = the files it highlights it seems to be an issue in the malloc:
https://= github.com/WayneD/rsync/blob/master/util2.c#L123

I've tested= to see if a local rsync mirror will cause the same error with random files= and found it happens at around 62 files being mirrored but size of the fil= e does not matter.
I run musll on multiple architectures and this= is the first time I've run across it and have confirmed the Gentoo gli= bc m68k install does not run into this.

--000000000000f0b63405ff0d709a--