From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: Test tree patch inventory - update
Date: Wed, 21 Nov 2007 00:21:03 +0000 [thread overview]
Message-ID: <20071121002103.GB24995@ghostprotocols.net> (raw)
In-Reply-To: <20071120201041.GA24995@ghostprotocols.net>
Em Sat, Nov 17, 2007 at 03:42:52PM +0000, Gerrit Renker escreveu:
> Test Tree Inventory
> =========
> 4. Support for passive-close without flushing unread data
> ---------------------------------------------------------
> This set actually involves only 5 patches, the last one is according to your suggestion.
>
> [DCCP]: Separate protocol states into general/specific
I dropped this one, see next explanation.
> [DCCP]: Make PARTOPEN an autonomous state
Here I made DCCP_PARTOPEN = TCP_MAX_STATES, that DCCP_INTRINSECS was not
used anywhere and this just means that states >= TCP_MAX_STATES are
DCCP only states.
> [DCCP]: Dedicated auxiliary states to support passive-close
I'll combine this with the next one.
> [DCCP]: Basic support for passive-close
What happens if we receive a second CloseReq or a second Close packet or
if the server performed an active close?
In all these cases we're leaking an skb, no? As dccp_rcv_close{req}
before always used dccp_fin there wasn't a need for returning a value
from these functions, but now we better return if we used the skb or
not, so that when back to __dccp_rcv_established and
dccp_rcv_state_process we can discard the packet.
- Arnaldo
next prev parent reply other threads:[~2007-11-21 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:10 Test tree patch inventory - update Arnaldo Carvalho de Melo
2007-11-21 0:21 ` Arnaldo Carvalho de Melo [this message]
2007-11-21 11:52 ` Gerrit Renker
2007-11-21 12:46 ` Arnaldo Carvalho de Melo
2007-11-21 13:18 ` Gerrit Renker
2007-11-22 10:29 ` Gerrit Renker
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=20071121002103.GB24995@ghostprotocols.net \
--to=acme@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.