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=-3.3 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 2253 invoked from network); 21 Dec 2023 03:38:02 -0000
Received: from second.openwall.net (193.110.157.125)
  by inbox.vuxu.org with ESMTPUTF8; 21 Dec 2023 03:38:02 -0000
Received: (qmail 8131 invoked by uid 550); 21 Dec 2023 03:37:19 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 8093 invoked from network); 21 Dec 2023 03:37:18 -0000
Date: Wed, 20 Dec 2023 22:38:01 -0500
From: Rich Felker <dalias@libc.org>
To: Cody Wetzel <codyawetzel@gmail.com>
Cc: musl@lists.openwall.com
Message-ID: <20231221033800.GI4163@brightrain.aerifal.cx>
References: <CAFj3ykfSQLcXxTKq3R=eWmgC9txKGmMwovkWGyXYgRQHRqyw9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFj3ykfSQLcXxTKq3R=eWmgC9txKGmMwovkWGyXYgRQHRqyw9Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] Segmentation fault musl 1.2.4

On Wed, Dec 20, 2023 at 03:53:38PM -0600, Cody Wetzel wrote:
> 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.

Without any indication of where the segfault was, it's impossible to
know whether it has anything to do with the change you cited or even
with musl. There is no reason oversized pages shouldn't function with
musl. They will lead to significantly worse memory usage and possibly
worse performance, but of course should not crash. Using 4k pages is
highly recommended if you have the option.

If you think the crash is caused by or related to a bug in musl,
please report what application is crashing and let us know if you can
use a debugger to get some basic information on the location of the
crash.

Rich