Date: Mon, 20 Jun 2016 12:14:18 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Gleb Smirnoff <glebius@FreeBSD.org>, Julien Charbon <jch@freebsd.org> Cc: rrs@FreeBSD.org, net@FreeBSD.org, current@FreeBSD.org Subject: Re: panic with tcp timers Message-ID: <b81aa248-4b97-3162-7636-da655163cdcc@selasky.org> In-Reply-To: <20160620095822.GJ1076@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b81aa248-4b97-3162-7636-da655163cdcc>