From owner-freebsd-amd64@freebsd.org  Mon May 16 20:46:23 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 4CD2BB3E381
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Mon, 16 May 2016 20:46:23 +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 3DB331DBC
 for <freebsd-amd64@FreeBSD.org>; Mon, 16 May 2016 20:46:23 +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 u4GKkMwi016322
 for <freebsd-amd64@FreeBSD.org>; Mon, 16 May 2016 20:46:23 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 209471] Listen queue overflow due to too many sockets stuck in
 CLOSED state
Date: Mon, 16 May 2016 20:46:23 +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.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: rblayzor@inoc.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-209471-6-ZXeXBMZOWk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209471-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209471-6@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-Mailman-Approved-At: Mon, 16 May 2016 21:29:12 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 20:46:23 -0000

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

--- Comment #11 from Robert Blayzor <rblayzor@inoc.net> ---
Bug 204426 references that review/patch. I did get the patch/diff and appli=
ed
it to 10.3. I've been running that for a week or two. While that corrected =
the
problem I originally saw in Bug 204426, now I see what is reported here. I'=
ve
been told the two are not related in the notes from 204426. Hence this PR.

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