From owner-freebsd-net@freebsd.org  Mon Jun 20 10:10:44 2016
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 BF6B7A7B123
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 20 Jun 2016 10:10:44 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id AC5DC2CD2
 for <freebsd-net@freebsd.org>; Mon, 20 Jun 2016 10:10:44 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id AB827A7B120; Mon, 20 Jun 2016 10:10:44 +0000 (UTC)
Delivered-To: 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 AB08CA7B11F;
 Mon, 20 Jun 2016 10:10:44 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214])
 (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 72C332CD1;
 Mon, 20 Jun 2016 10:10:43 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 0FCB81FE023;
 Mon, 20 Jun 2016 12:10:40 +0200 (CEST)
Subject: Re: panic with tcp timers
To: Gleb Smirnoff <glebius@FreeBSD.org>, Julien Charbon <jch@freebsd.org>
References: <20160617045319.GE1076@FreeBSD.org>
 <1f28844b-b4ea-b544-3892-811f2be327b9@freebsd.org>
 <20160620073917.GI1076@FreeBSD.org>
 <1d18d0e2-3e42-cb26-928c-2989d0751884@freebsd.org>
 <20160620095822.GJ1076@FreeBSD.org>
Cc: rrs@FreeBSD.org, net@FreeBSD.org, current@FreeBSD.org
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <b81aa248-4b97-3162-7636-da655163cdcc@selasky.org>
Date: Mon, 20 Jun 2016 12:14:18 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <20160620095822.GJ1076@FreeBSD.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.22
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: Mon, 20 Jun 2016 10:10:44 -0000

On 06/20/16 11:58, Gleb Smirnoff wrote:
> The fix I am working on now is doing exactly that. callout_reset must
> return 0 if the callout is currently running.
>
> What are the old paths impacted?

Hi,

I'll dig into the matter aswell and give some comments. Thanks for the 
analysis, Gleb.

FYI: This class of problems wouldn't exist if the callout could be 
associated with a mutex!

--HPS