From owner-freebsd-arm@FreeBSD.ORG  Sun Nov  3 14:13:55 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 3FCFE1D8;
 Sun,  3 Nov 2013 14:13:55 +0000 (UTC) (envelope-from db@db.net)
Received: from diana.db.net (unknown [IPv6:2620:64:0:1:223:7dff:fea2:c8f2])
 by mx1.freebsd.org (Postfix) with ESMTP id 21AE220CE;
 Sun,  3 Nov 2013 14:13:55 +0000 (UTC)
Received: from night.db.net (localhost [127.0.0.1])
 by diana.db.net (Postfix) with ESMTP id 63CA92AA45F;
 Sun,  3 Nov 2013 07:13:52 -0700 (MST)
Received: by night.db.net (Postfix, from userid 1000)
 id 5934D1CC18; Sun,  3 Nov 2013 09:13:21 -0500 (EST)
Date: Sun, 3 Nov 2013 09:13:21 -0500
From: Diane Bruce <db@db.net>
To: Ian Lepore <ian@FreeBSD.org>
Subject: Re: sshd crash
Message-ID: <20131103141321.GA57218@night.db.net>
References: <CAAvnz_rj43Ww6=mMfnp2u5TA2pWb20vWOqyAtuK08wgzy0dH6A@mail.gmail.com>
 <1383313834.31172.65.camel@revolution.hippie.lan>
 <CAHNYxxMMF_GJv10drYuQFO+av+Tdp8OBvJfFZObEZ=tgaBovSA@mail.gmail.com>
 <1383328423.31172.92.camel@revolution.hippie.lan>
 <CAHNYxxNiuKP8wfTaZuL+BXiLcYA9eU3LBb-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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131102153953.GA39106@night.db.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Tim Kientzle <tim@kientzle.com>, jasone@FreeBSD.org,
 freebsd-arm@FreeBSD.org, Howard Su <howard0su@gmail.com>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Nov 2013 14:13:55 -0000

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