From owner-freebsd-bugs@FreeBSD.ORG  Wed Jan  7 08:07:36 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 299C5C70
 for <freebsd-bugs@FreeBSD.org>; Wed,  7 Jan 2015 08:07:36 +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 104F366170
 for <freebsd-bugs@FreeBSD.org>; Wed,  7 Jan 2015 08:07:36 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0787ZNr096354
 for <freebsd-bugs@FreeBSD.org>; Wed, 7 Jan 2015 08:07:35 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: Wed, 07 Jan 2015 08:07:36 +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-G9SIUCDGKT@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: Wed, 07 Jan 2015 08:07:36 -0000

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

--- Comment #12 from Arne Claus <arne.claus@trivago.com> ---
We're now running tests with the following configuration

FreeBSD 10.1-RELEASE (GENERIC) #0 r274401
memcached 1.4.22
libevent 2.0.21-stable

As of now everything works fine, so the situation has at least improved.
As I did not see any directly related changes on the FreeBSD changelog (the TCP
fixes seem not be relevant for this case) my current assumption is that changes
in memcached 1.4.22 fixed the issue. I did not test 1.4.22 on FreeBSD 10.0
though.

As the bug shows signs of a race condition especially the threading fixes in
memcached 1.4.22 are good candidates for having fixed the issue:
https://code.google.com/p/memcached/wiki/ReleaseNotes1422#Memcached_1.4.22_Release_Notes

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