Date: Sun, 3 Nov 2013 09:13:21 -0500 From: Diane Bruce <db@db.net> To: Ian Lepore <ian@FreeBSD.org> Cc: Tim Kientzle <tim@kientzle.com>, jasone@FreeBSD.org, freebsd-arm@FreeBSD.org, Howard Su <howard0su@gmail.com> Subject: Re: sshd crash Message-ID: <20131103141321.GA57218@night.db.net> In-Reply-To: <20131102153953.GA39106@night.db.net> References: <CAAvnz_rj43Ww6=mMfnp2u5TA2pWb20vWOqyAtuK08wgzy0dH6A@mail.gmail.com> <1383313834.31172.65.camel@revolution.hippie.lan> <CAHNYxxMMF_GJv10drYuQFO%2Bav%2BTdp8OBvJfFZObEZ=tgaBovSA@mail.gmail.com> <1383328423.31172.92.camel@revolution.hippie.lan> <CAHNYxxNiuKP8wfTaZuL%2BBXiLcYA9eU3LBb-659ZBYr-WBSmZeQ@mail.gmail.com> <1383343354.31172.102.camel@revolution.hippie.lan> <EB18203F-C516-4917-9AA4-DBA6E66DAAB6@kientzle.com> <1383399220.31172.116.camel@revolution.hippie.lan> <20131102153953.GA39106@night.db.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 02, 2013 at 10:39:53AM -0500, Diane Bruce wrote: ... > > > If I recall correctly, it started up when the malloc libc symbols > > > were changed. That may have altered what malloc implementation > > > sshd used. > > > > > > So it could be a long-standing stray write that jemalloc just > > > happens to detect. > > > > > > It could also be related to locking (there's some multi-threaded > > > crypto code in sshd that may be involved). ... > > http://svnweb.freebsd.org/base?view=revision&revision=250991 > > > > When jemalloc was turned on for userland. There existed an older malloc > (also by jasone) > > /usr/src/lib/libc/stdlib/malloc.c I made a rushed mistake here. What happens is there is a simple version of malloc in libexec/rtld-elf that gets used if jemalloc is not used. This version works fine. /* * malloc.c (Caltech) 2/21/82 * Chris Kingsley, kingsley@cit-20. ... - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131103141321.GA57218>