From owner-freebsd-bugs@FreeBSD.ORG  Thu Jan 15 13:47:50 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 50AFA1C1
 for <freebsd-bugs@FreeBSD.org>; Thu, 15 Jan 2015 13:47:50 +0000 (UTC)
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 38554395
 for <freebsd-bugs@FreeBSD.org>; Thu, 15 Jan 2015 13:47:50 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FDlod0019649
 for <freebsd-bugs@FreeBSD.org>; Thu, 15 Jan 2015 13:47:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192889] accept4 socket hangs in CLOSED (memcached)
Date: Thu, 15 Jan 2015 13:47:49 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: arne.claus@trivago.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192889-8-FcUZu8lD2r@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192889-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192889-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 13:47:50 -0000

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

--- Comment #14 from Arne Claus <arne.claus@trivago.com> ---
We tested memcached 1.4.20 again on FreeBSD 10.1 and this version does not show
any hangs, too. So at the moment it looks like something on the FreeBSD side
caused the issue.

It would be great if someone with a little more knowledge on the network topic
could post an overview on what changed in the network stack / accept chain for
FreeBSD 10.1 so we can pin down the problem a little bit more.
The current state is a little bit uncomfortable as memcached now seems to run
stable but nobody knows why.
The FreeBSD changelog only lists some security issue in the TCP/IP stack but
those do not seem very related (I did not see the code though).

-- 
You are receiving this mail because:
You are the assignee for the bug.