From owner-freebsd-current@freebsd.org  Mon Mar 14 22:25:48 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 111DAAD13E5
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 14 Mar 2016 22:25:48 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id CE086CE3
 for <freebsd-current@freebsd.org>; Mon, 14 Mar 2016 22:25:47 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 7A9BB4F57A;
 Mon, 14 Mar 2016 22:25:40 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u2EMPcaC018157;
 Mon, 14 Mar 2016 22:25:38 GMT (envelope-from phk@phk.freebsd.dk)
To: Larry Rosenman <ler@lerctr.org>
cc: Konstantin Belousov <kostikbel@gmail.com>,
 Freebsd current <freebsd-current@freebsd.org>
Subject: Re: Crashes in libthr?
In-reply-to: <20160314222228.GA1753@borg.lerctr.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <276f6b11da9a005256d24fa5b37d7d5f@thebighonker.lerctr.org>
 <20160313185852.GJ1741@kib.kiev.ua>
 <ddea502af186ce26273fddc9360e45cf@thebighonker.lerctr.org>
 <20160313192900.GK1741@kib.kiev.ua>
 <b3caf0652b0cbcb2edb7ebac0c3ded97@thebighonker.lerctr.org>
 <20160314025123.GA74197@borg.lerctr.org> <20160314065348.GM1741@kib.kiev.ua>
 <d1eaa340b30b635f23fffdda35981d9d@thebighonker.lerctr.org>
 <20160314221018.GA2211@borg.lerctr.org> <20160314221745.GT1741@kib.kiev.ua>
 <20160314222228.GA1753@borg.lerctr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18155.1457994338.1@critter.freebsd.dk>
Date: Mon, 14 Mar 2016 22:25:38 +0000
Message-ID: <18156.1457994338@critter.freebsd.dk>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2016 22:25:48 -0000

--------
In message <20160314222228.GA1753@borg.lerctr.org>, Larry Rosenman writes:

>And sshd is busted. 

FYI: I seeing no such issues on two systems running:

	11.0-CURRENT #4 r296808: Sun Mar 13 22:39:59 UTC 2016
and
	11.0-CURRENT #32 r296137: Sat Feb 27 11:34:01 UTC 2016 

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.