From owner-freebsd-current@FreeBSD.ORG Tue Mar 17 22:45:59 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 980AA128; Tue, 17 Mar 2015 22:45:59 +0000 (UTC) Received: from relay.mailchannels.net (ar-005-i194.relay.mailchannels.net [162.253.144.76]) by mx1.freebsd.org (Postfix) with ESMTP id 390CBAAA; Tue, 17 Mar 2015 22:45:56 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp5.ore.mailhop.org (ip-10-229-11-165.us-west-2.compute.internal [10.229.11.165]) by relay.mailchannels.net (Postfix) with ESMTPA id 2C9CC1D0350; Tue, 17 Mar 2015 19:17:54 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp5.ore.mailhop.org (smtp5.ore.mailhop.org [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Tue, 17 Mar 2015 19:17:55 +0000 X-MC-Relay: Bad X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426619875247:912503956 X-MC-Ingress-Time: 1426619875247 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp5.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YXwzv-0000eq-Po; Tue, 17 Mar 2015 19:17:51 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2HJHorn026199; Tue, 17 Mar 2015 13:17:50 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX18QmaueKsk7NDKGsve4Kot4 Message-ID: <1426619869.62241.5.camel@freebsd.org> Subject: Re: sbuf-related panic From: Ian Lepore To: Mark Felder Date: Tue, 17 Mar 2015 13:17:49 -0600 In-Reply-To: <1426619679.676332.241672369.5773381C@webmail.messagingengine.com> References: <1426529019.4766.1.camel@hardenedbsd.org> <1426618197.670703.241661961.0D1A6F14@webmail.messagingengine.com> <1426618644.62241.4.camel@freebsd.org> <1426619679.676332.241672369.5773381C@webmail.messagingengine.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 22:45:59 -0000 On Tue, 2015-03-17 at 14:14 -0500, Mark Felder wrote: > > On Tue, Mar 17, 2015, at 13:57, Ian Lepore wrote: > > On Tue, 2015-03-17 at 13:49 -0500, Mark Felder wrote: > > > > > > On Mon, Mar 16, 2015, at 13:03, Shawn Webb wrote: > > > > On amd64, doing a Poudriere run. On r280133: > > > > > > > > > > I appeared to be hitting this on 280130, the most recent CURRENT > > > snapshot. I'm going to build the latest since some sbuf fixes have > > > landed and see if I can finish a poudriere build run. > > > > There is still a panic, one that I can't yet figure out why it wasn't > > panicking before my changes, but I'm working on it. > > > > Is the previous snapshot -- r279813 -- old enough to have missed the > related changes? I'm just trying to get a machine up from 10.1-RELEASE > to relatively CURRENT quickly. That should be safe, my series of sbuf changes that broke things started at r279992. -- Ian