Date: Tue, 3 Jun 2014 10:18:42 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Julien Charbon <jcharbon@verisign.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: [rfc] TCP timewait and credential handling - why would we get a TW with no credential? Message-ID: <CAJ-Vmo==ge2_Lj8Cj6v6qsmCFyTg8ixGHqQbX8wcT4dReVtW-A@mail.gmail.com> In-Reply-To: <538DA6A6.6040201@verisign.com> References: <CAJ-Vmo=JwL7gFE2xfXa9cx4rYdkDf87qoy32H%2BSguRPogT2p=w@mail.gmail.com> <538DA6A6.6040201@verisign.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[snip] Hm, lemme try adding some debugging to the tw_cred = crhold() bit to see if it assigns a NULL pointer. I've noticed that I'm getting NULL capability sets when doing some kqueue stuff and it causes it to return with ENOCAPABLE on newly created sockets that I'm trying to set write readiness on. Maybe this is related. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo==ge2_Lj8Cj6v6qsmCFyTg8ixGHqQbX8wcT4dReVtW-A>