Date: Sat, 28 Jan 2017 14:43:16 +0000 From: Tom Vijlbrief <tvijlbrief@gmail.com> To: Shawn Webb <shawn.webb@hardenedbsd.org>, Andrew Turner <andrew@fubar.geek.nz> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Arm64 stack issues (was Re: FreeBSD status for/on ODroid-C2?) Message-ID: <CAOQrpVfxKvSR5PoahnqEsYspHhjjOGJ8iCBUetKxRV57oX_aUg@mail.gmail.com> In-Reply-To: <20170128010223.tjivldnh7pyenbg6@mutt-hardenedbsd> References: <CAOQrpVfK-Dw_rSo_YVY5MT1wbc6Ah-Pj%2BWv8UGjeiUQ1b3%2B-mg@mail.gmail.com> <20170124191357.0ec0abfd@zapp> <20170128010138.iublazyrhhqycn37@mutt-hardenedbsd> <20170128010223.tjivldnh7pyenbg6@mutt-hardenedbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
Did a build/install world/kernel with r312916 and MALLOC_PRODUCTION=YES on a pine64, removed /etc/malloc.conf, rebooted and I am now rebuilding the python2 port without problems so far (except the "gic0: Spurious interrupt detected" messages which reappeared shortly after my previous post) Op za 28 jan. 2017 om 02:02 schreef Shawn Webb <shawn.webb@hardenedbsd.org>: > On Fri, Jan 27, 2017 at 08:01:38PM -0500, Shawn Webb wrote: > > On Tue, Jan 24, 2017 at 07:13:57PM +0000, Andrew Turner wrote: > > > Can you try with r312703 and without the malloc.conf change? I think > the > > > issue was because errno was stored just before some internal jemalloc > > > state in the bss and there was a bug where the setting of errno where > > > it would overwrite 32 bits of this state. > > > > I've just tested on an RPI3 and tcache still needs to be disabled with > > malloc.conf. > > I misspoke somewhat: the testing was done on a SoftIron Overdrive 1000. > > -- > Shawn Webb > Cofounder and Security Engineer > HardenedBSD > > GPG Key ID: 0x6A84658F52456EEE > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOQrpVfxKvSR5PoahnqEsYspHhjjOGJ8iCBUetKxRV57oX_aUg>