Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Oct 2014 07:35:44 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        Sean Bruno <sbruno@llnw.com>, FreeBSD Net <freebsd-net@freebsd.org>, Jason Wolfe <nitroboost@gmail.com>
Subject:   Re: ixgbe(4) spin lock held too long
Message-ID:  <4003470.qylyPxsqMt@ralph.baldwin.cx>
In-Reply-To: <CAJ-VmomMCP%2BXFKEu-tCc_A3z5NatsTXEqQUKg3mc2pcMzH%2BnGA@mail.gmail.com>
References:  <1410203348.1343.1.camel@bruno> <CAAAm0r2x%2BVJafG1LDixpgj9RjeVaXpJ5UMA3EzAcN3DqX5hxzA@mail.gmail.com> <CAJ-VmomMCP%2BXFKEu-tCc_A3z5NatsTXEqQUKg3mc2pcMzH%2BnGA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, October 17, 2014 11:43:26 PM Adrian Chadd wrote:
> Hm, is this the bug that was just fixed in -HEAD?
> 
> I saw this similar bug on -HEAD with lots of quick connections and
> reused ports. It ended up deferencing a NULL tcp timer pointer from
> the inpcb. Is that what the code in your tree is doing?

This is not a NULL tcp timer pointer.  Instead, the retransmit timer is being 
armed while the persist timer is still armed.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4003470.qylyPxsqMt>