All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: DCCP_BUG called
Date: Fri, 20 Aug 2010 10:40:29 +0000	[thread overview]
Message-ID: <20100820104028.GA3438@gerrit.erg.abdn.ac.uk> (raw)
In-Reply-To: <4C6D3DD8.4080606@pu-pm.univ-fcomte.fr>

>> I haven't verified this, but I am almost sure that the problem is rectified in the
>> DCCP test tree which I would like to encourage you to use for all testing, since it
>
> Thank you for your answer.  I have not yet tested with DCCP test tree  
> indeed, but I see that the code involved is there too, i.e.:
>
>  306  err = dccp_transmit_skb(sk, skb);
>  307  ccid_hc_tx_packet_sent(dp->dccps_hc_tx_ccid, sk, 0, len);
>  308  if (err)
>  309    DCCP_BUG("err=%d after ccid_hc_tx_packet_sent",
>  310             err);
>

Agree, in this case it will also trigger the BUG warning. It seems that it rather should be 

   if (err < 0)
      DCCP_BUG(...)

but I need to go through this at home. One reason why this is there is the congestion control.

The assumption in hc_tx_packet_sent() is normally that the packet has been sent, there is no
second function to register packets that have not been sent. That case is treated as if the
packet got lost in the network, i.e. the loss is registered later, via the receiver feedback.

Hence it seems to me that we can remove this, or replace by a debug/warning statement.


Thanks a lot for reporting the issue, I will reply again Monday.
Gerrit

  parent reply	other threads:[~2010-08-20 10:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 14:21 DCCP_BUG called Eugen Dedu
2010-08-20  5:15 ` Gerrit Renker
2010-08-20  8:46 ` Eugen Dedu
2010-08-20 10:40 ` Gerrit Renker [this message]
2010-08-23  5:29 ` Gerrit Renker
2010-08-25 13:21 ` Eugen Dedu
2010-08-26 11:08 ` gerrit
2010-08-26 16:11 ` Eugen Dedu
2010-08-26 16:26 ` Ian McDonald
2010-08-26 20:12 ` Eugen Dedu
2010-08-27 11:45 ` Gerrit Renker
2010-08-27 13:32 ` Eugen Dedu
2010-08-30 17:33 ` Ian McDonald

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=20100820104028.GA3438@gerrit.erg.abdn.ac.uk \
    --to=gerrit@erg.abdn.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 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.