mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Immolo <immoloism@googlemail.com>
To: musl@lists.openwall.com
Subject: [musl] m68k - malloc causing 'out of memory: my_alloc caller' in rsync
Date: Mon, 26 Jun 2023 20:34:04 +0100	[thread overview]
Message-ID: <CAHfWF5=VMiqHsJ0c3uSHVz2SdFzhF-+mp=jeyxfFDeySKBxhUQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 2295 bytes --]

             reply	other threads:[~2023-06-26 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 19:34 Immolo [this message]
2023-06-26 21:06 ` Rich Felker
2023-07-19 13:40   ` Immolo

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='CAHfWF5=VMiqHsJ0c3uSHVz2SdFzhF-+mp=jeyxfFDeySKBxhUQ@mail.gmail.com' \
    --to=immoloism@googlemail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).