From owner-freebsd-net@freebsd.org  Thu Feb  2 01:45:11 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 4DA0ACCB59B
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu,  2 Feb 2017 01:45:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3CD2C1574
 for <freebsd-net@FreeBSD.org>; Thu,  2 Feb 2017 01:45:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v121jAnt015350
 for <freebsd-net@FreeBSD.org>; Thu, 2 Feb 2017 01:45:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 204340] [panic] nfsd, em, msix, fatal trap 9
Date: Thu, 02 Feb 2017 01:45:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: IntelNetworking, crash, patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: rmacklem@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org
X-Bugzilla-Flags: mfc-stable9- mfc-stable10+
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-204340-2472-xPTHehkyxP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204340-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-204340-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 01:45:11 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204340

--- Comment #23 from Rick Macklem <rmacklem@FreeBSD.org> ---
Created attachment 179512
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D179512&action=
=3Dedit
add svcpool_close so that svcpool_destroy doesn't get called when nfsd thre=
ads
are killed

This patch adds a new function to the server krpc called svcpool_close().
It is similar to svcpool_destroy(), but does not free the data structures,
so that the pool can be used again.

This function is then used instead of svcpool_destroy(), svcpool_create()
when the nfsd threads are killed.

These crashes are caused because the data structures were free'd by
svcpool_destroy() when the nfsd threads were killed off (or signalled someh=
ow).
By avoiding the svcpool_destroy() call, the crashes should be avoided.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=