From owner-freebsd-net@FreeBSD.ORG  Tue Jun  3 17:18:44 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2765C8A4
 for <freebsd-net@freebsd.org>; Tue,  3 Jun 2014 17:18:44 +0000 (UTC)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com
 [IPv6:2607:f8b0:400d:c00::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id DC17E2197
 for <freebsd-net@freebsd.org>; Tue,  3 Jun 2014 17:18:43 +0000 (UTC)
Received: by mail-qa0-f48.google.com with SMTP id i13so5401586qae.35
 for <freebsd-net@freebsd.org>; Tue, 03 Jun 2014 10:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=AsrdcF6LUdXjfmDm2pG9cSdg4Ah6/zJVi5lc6Y1sF4E=;
 b=oKmhEG1+YrltRTqxb29AET9K64547jVAsW6+/XkKZIAyCYCtyLD/OrryWIEreb4Y4J
 1IirF9uCnBXSipP4wX9FutTAVgQ+Zxm2oZI5bFQpJBmQRU7GjoE9cq5OYQUKLJzn4F72
 G773BgWdYe9IzBCM2qRtwY1+/V4ZZWOTPouPLAVJGE8QRrgrF5ZI8DOn4YIG1IU2uS0n
 Zb4oAmsZEyS3JW5hxr0B/Bfd+NYSVwh3Fs/zRUVWOn4ls6zEah8lyJ136ipQJ4XBBW3x
 Yn0Nnlx+qFetMD5zIsJOnXbVF/tKJ7zIBe8tB9Xh6efjmLi2ObYHUCjc14ZwTLFSzTJg
 bl/A==
MIME-Version: 1.0
X-Received: by 10.224.43.148 with SMTP id w20mr63778066qae.26.1401815922903;
 Tue, 03 Jun 2014 10:18:42 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.224.43.134 with HTTP; Tue, 3 Jun 2014 10:18:42 -0700 (PDT)
In-Reply-To: <538DA6A6.6040201@verisign.com>
References: <CAJ-Vmo=JwL7gFE2xfXa9cx4rYdkDf87qoy32H+SguRPogT2p=w@mail.gmail.com>
 <538DA6A6.6040201@verisign.com>
Date: Tue, 3 Jun 2014 10:18:42 -0700
X-Google-Sender-Auth: iYEZRbv9eKHKhJsYg5gOJrwt9Mk
Message-ID: <CAJ-Vmo==ge2_Lj8Cj6v6qsmCFyTg8ixGHqQbX8wcT4dReVtW-A@mail.gmail.com>
Subject: Re: [rfc] TCP timewait and credential handling - why would we get a
 TW with no credential?
From: Adrian Chadd <adrian@freebsd.org>
To: Julien Charbon <jcharbon@verisign.com>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD Net <freebsd-net@freebsd.org>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 17:18:44 -0000

[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