From: Andrea Bittau <a.bittau@cs.ucl.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [BUG] Problem with feature negotiation
Date: Tue, 14 Feb 2006 08:20:08 +0000 [thread overview]
Message-ID: <20060214082008.GA6572@tribal.sorbonet.org> (raw)
In-Reply-To: <cbec11ac0602131606r3db89cbcp2fba640d61b92447@mail.gmail.com>
On Tue, Feb 14, 2006 at 01:06:47PM +1300, Ian McDonald wrote:
> If either of you too can fix that it'd be cool otherwise I'll add it
> to my list of rainy day bugs....
I'll look into it myself. I've been caught up on other stuff, so I wasn't able
to do much DCCP work lately. I will very soon though [towards the end of the
week].
The last thing I was playing with was trying to fix the module reference count.
For some reason, I think there is an invalid reference count for client sockets.
This does not let you unload the module, which is painful for development.
Also, does anyone know if there is the equivalent of BSD divert sockets for
Linux? I was planning to use those for making a DCCP test suite. The
motivation is that you can intercept, inspect and drop packets.
prev parent reply other threads:[~2006-02-14 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 0:06 [BUG] Problem with feature negotiation Ian McDonald
2006-02-14 8:20 ` Andrea Bittau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060214082008.GA6572@tribal.sorbonet.org \
--to=a.bittau@cs.ucl.ac.uk \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox