From: Cody Wetzel <codyawetzel@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: musl@lists.openwall.com, Markus Wichmann <nullplan@gmx.net>
Subject: Re: [musl] Segmentation fault musl 1.2.4
Date: Wed, 3 Jan 2024 11:20:29 -0600 [thread overview]
Message-ID: <CAFj3ykcn8F0w-Wkki4eZQ6-vDiz4oo9ZjhMiM41KJa=PR11eZA@mail.gmail.com> (raw)
In-Reply-To: <CAFj3yke_pv=bzbfDeA07-dYORYzU_fLAdwbwQbOL-Q-w+hYkHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4508 bytes --]
Hello musl team,
I tried getting a core dump but I'm not sure if I'm doing something wrong...
/ # cat /proc/sys/kernel/core_pattern/tmp/core-%e-%s-%u-%g-%p-%t/ #
apk upgrade busybox
--repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/main
--repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/communityfetch
https://dl-cdn.alpinelinux.org/alpine/v3.18/community/armv7/APKINDEX.tar.gzfetch
https://dl-cdn.alpinelinux.org/alpine/v3.18/main/armv7/APKINDEX.tar.gzfetch
https://dl-cdn.alpinelinux.org/alpine/v3.17/main/armv7/APKINDEX.tar.gzfetch
https://dl-cdn.alpinelinux.org/alpine/v3.17/community/armv7/APKINDEX.tar.gz(1/3)
Upgrading busybox (1.35.0-r29 -> 1.36.1-r5)Executing
busybox-1.36.1-r5.post-upgrade(2/3) Upgrading busybox-binsh
(1.35.0-r29 -> 1.36.1-r5)(3/3) Upgrading ssl_client (1.35.0-r29 ->
1.36.1-r5)Executing busybox-1.36.1-r5.triggerOK: 5 MiB in 15 packages/
# apk upgrade musl
--repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/main
--repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/community(1/1)
Upgrading musl (1.2.3-r5 -> 1.2.4-r2)OK: 5 MiB in 15 packages/ # apk
upgrade rust --repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/main
--repository=https://dl-cdn.alpinelinux.org/alpine/v3.18/communitySegmentation
fault/ # apk -hSegmentation fault/ # ls /tmp/core*Segmentation fault/
# cd /tmp/tmp # lsSegmentation fault
>
>
Thanks!
Cody
On Thu, Dec 21, 2023 at 3:57 PM Cody Wetzel <codyawetzel@gmail.com> wrote:
> I am able to run:
>
> # apk upgrade busybox --repository=
> https://dl-cdn.alpinelinux.org/alpine/v3.18/main --repository=
> https://dl-cd
> n.alpinelinux.org/alpine/v3.18/community
>
> and not create a segmentation fault on Alpine 3.17
>
> I will be on Christmas vacation for the next week but when I get back I
> can try to get additional details.
>
> Thanks!
>
> Cody
>
> On Thu, Dec 21, 2023 at 3:25 PM Natanael Copa <ncopa@alpinelinux.org>
> wrote:
>
>> On Thu, 21 Dec 2023 12:39:35 -0600
>> Cody Wetzel <codyawetzel@gmail.com> wrote:
>>
>> > Markus,
>> >
>> > No kidding. I've been dealing with issues running Home Assistant for
>> quite
>> > some time thanks to this page size change. Since I'm not the most well
>> > versed in Linux I will need to look into how to get logs. I do have a
>> > Github issue you can look at for more details in the meantime.
>> >
>> > https://github.com/home-assistant/core/issues/86589
>>
>> Those issues will keep popping up til we fix them, and to fix them we
>> will need to know exactly what to fix, a backtrace may help with that.
>> Alternatively we'd need a simple way to reproduce the issue.
>>
>> I found this following the above issue:
>> https://gitlab.alpinelinux.org/alpine/aports/-/issues/15167
>> This issue looks more like a problem in busybox than musl.
>>
>> -nc
>>
>>
>> > Note that I think there is an issue in rustc also.
>> >
>> > Thanks!
>> >
>> > Cody
>> >
>> > On Thu, Dec 21, 2023 at 1:57*AM Markus Wichmann <nullplan@gmx.net>
>> > wrote:
>> >
>> > > Am Wed, Dec 20, 2023 at 03:53:38PM -0600 schrieb Cody Wetzel:
>> > > > Hello,
>> > > >
>> > > > I am running into a segmentation fault on musl 1.2.4 on my QNAP
>> > > > NAS.
>> > > QNAP
>> > > > updated the pagesize to 32k and I believe musl isn't handling it
>> > > > gracefully. musl 1.2.3 does not have this problem.
>> > > >
>> > > >
>> > >
>> https://www.qnap.com/da-dk/how-to/faq/article/why-do-the-installed-third-party-containers-not-run-successfully-on-specific-32-bit-arm-devices
>> > >
>> > > >
>> > > > Please CC me.
>> > > >
>> > > > --
>> > > > Cody Wetzel
>> > > > codyawetzel@gmail.com
>> > > > (402)490-9242
>> > >
>> > > Gonna try my luck since Rich apparently had none: Please procure
>> > > some data from the crash, such as a core dump or a backtrace.
>> > > Without any indication of what is going on, there is no telling
>> > > whether the issue you are experiencing even is in musl, let alone
>> > > where it is.
>> > >
>> > > BTW, the linked website is a hoot and a half. "We made this change
>> > > to improve your user experience, but it may cause your applications
>> > > to have less memory and also crash. Your only recourse is to 'Verify
>> > > compatibility', i.e. sink or swim."
>> > >
>> > > Ciao,
>> > > Markus
>> > >
>> >
>> >
>>
>>
>
> --
> Cody Wetzel
> codyawetzel@gmail.com
> (402)490-9242
>
--
Cody Wetzel
codyawetzel@gmail.com
(402)490-9242
[-- Attachment #2: Type: text/html, Size: 9559 bytes --]
next prev parent reply other threads:[~2024-01-03 17:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 21:53 Cody Wetzel
2023-12-21 3:38 ` Rich Felker
2023-12-21 4:15 ` Rich Felker
2023-12-21 7:57 ` Markus Wichmann
2023-12-21 18:39 ` Cody Wetzel
2023-12-21 21:25 ` Natanael Copa
2023-12-21 21:57 ` Cody Wetzel
2024-01-03 17:20 ` Cody Wetzel [this message]
2024-01-03 17:26 ` Leah Neukirchen
2024-01-03 18:00 ` Cody Wetzel
2024-01-04 14:48 ` Szabolcs Nagy
2024-01-10 15:59 ` Cody Wetzel
2024-01-11 17:03 ` Szabolcs Nagy
2024-01-11 18:19 ` Cody Wetzel
2024-01-12 18:57 ` Szabolcs Nagy
2024-01-12 23:10 ` Cody Wetzel
2024-01-15 22:30 ` Szabolcs Nagy
2024-01-16 15:21 ` Cody Wetzel
2024-01-16 18:29 ` Szabolcs Nagy
2024-01-16 18:53 ` Cody Wetzel
2024-01-16 20:45 ` Rich Felker
2024-01-30 10:43 ` Szabolcs Nagy
2024-01-30 15:37 ` Rich Felker
2024-01-30 20:17 ` [musl] Fixing ELF loader for systems with oversized pages [was: Re: [musl] Segmentation fault musl 1.2.4] Rich Felker
2023-12-22 2:20 ` [musl] Segmentation fault musl 1.2.4 Jeffrey Walton
2023-12-22 2:22 ` Jeffrey Walton
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='CAFj3ykcn8F0w-Wkki4eZQ6-vDiz4oo9ZjhMiM41KJa=PR11eZA@mail.gmail.com' \
--to=codyawetzel@gmail.com \
--cc=musl@lists.openwall.com \
--cc=ncopa@alpinelinux.org \
--cc=nullplan@gmx.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.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).