From owner-freebsd-current@freebsd.org  Mon Aug 24 06:13:47 2015
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 D817A9C1B05
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 24 Aug 2015 06:13:47 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 9811F1E7C;
 Mon, 24 Aug 2015 06:13:46 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA11681;
 Mon, 24 Aug 2015 09:13:43 +0300 (EEST)
 (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1ZTl0o-000IQK-Te; Mon, 24 Aug 2015 09:13:42 +0300
Subject: Re: Instant panic while trying run ports-mgmt/poudriere
To: Konstantin Belousov <kostikbel@gmail.com>
References: <20150713231205.627bab36@FreeBSD.org>
 <20150714223829.GY8523@funkthat.com> <20150715174616.652d0aea@FreeBSD.org>
 <20150715180526.GM8523@funkthat.com> <20150715223703.78b9197c@FreeBSD.org>
 <CAHM0Q_PLRP4t6JgkstXHNOVV+2DyathOgi8bg4-RQkW-BcGXow@mail.gmail.com>
 <20150806233328.47a02594@FreeBSD.org> <55CB5428.2090505@room52.net>
 <55D96E24.9060106@FreeBSD.org> <20150823090816.GJ2072@kib.kiev.ua>
 <20150823125442.GK2072@kib.kiev.ua>
Cc: John-Mark Gurney <jmg@funkthat.com>,
 FreeBSD Current <freebsd-current@FreeBSD.org>,
 Lawrence Stewart <lstewart@room52.net>,
 Pawel Pekala <pawel@FreeBSD.org>, "K. Macy" <kmacy@FreeBSD.org>
From: Andriy Gapon <avg@FreeBSD.org>
Message-ID: <55DAB5DB.5090008@FreeBSD.org>
Date: Mon, 24 Aug 2015 09:12:43 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20150823125442.GK2072@kib.kiev.ua>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
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, 24 Aug 2015 06:13:47 -0000

On 23/08/2015 15:54, Konstantin Belousov wrote:
> After looking at your data closely, I think you are right.  The panic
> occurs when the exit1(9) does KNOTE_LOCKED(NOTE_EXIT).  This is the
> only case in the tree where filter uses knlist_remove_inevent() to detach
> processed note, so indeed the slist is modified under the iterator.
> 
> Below is the patch with the suggested change and unrelated cleanup of
> the uma(9) KPI use.  Please test, everybody who has a panic with the
> backtrace pointing to the sys_exit().

Thank you very much!
I no longer get the panic in the test case that previously triggered it.

-- 
Andriy Gapon