From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: David Miller <davem@davemloft.net>
Cc: dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: [Patch 0/6] [dccp]: DCCP bug-fixes for net-2.6 (revision 01)
Date: Wed, 11 Jun 2008 11:36:47 +0100 [thread overview]
Message-ID: <20080611103647.GD8403@gerrit.erg.abdn.ac.uk> (raw)
In-Reply-To: <20080610.123236.158548229.davem@davemloft.net>
Hi David,
please consider the revised set of DCCP Bug-Fix patches
(changelog below), which can be pulled from:
git://eden-feed.erg.abdn.ac.uk/net-2.6
All patches are in branch `master', on top of a freshly cloned net-2.6 tree.
Result has been compile-tested again.
List of changes introduced in this submission
---------------------------------------------
Relative to yesterday's submission, only these things have changed:
* rewrote and updated the commit message of the first patch, which was
referencing a SHA1 ID only. This now has data and commit information added;
* removed the request-sock initialisation patch, since this has already been
fixed in your tree.
View-ability of changes
-----------------------
Since there are no code changes, I omit sending all the patches again. But
the differences can in any case be viewed on
http://eden-feed.erg.abdn.ac.uk/cgi-bin/gitweb.cgi?p=net-2.6.git;a=summary
List of patches included in this set:
-------------------------------------
Patch #1: Fixes a divide-by-zero bug in CCID-3.
Patch #2: Resolves sparse warnings (gathered from several patches in the tree).
Patch #3: Enforces that Ack Vectors are not interpreted on request sockets.
Patch #4: Computation error in CCID-3 allowed sending rate.
Patch #5: Sending rate in CCID-3 truncated due to u64 -> u32 conversion.
Patch #6: Typo in initial sequence number assignment.
next prev parent reply other threads:[~2008-06-11 10:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dccp_bug_fixes_for_net-2.6>
2008-06-10 12:53 ` [Patch 0/7] [dccp]: DCCP bug-fixes for net-2.6 Gerrit Renker
2008-06-10 12:53 ` [PATCH 1/7] dccp ccid-3: Bug-Fix - Zero RTT is possible Gerrit Renker
2008-06-10 12:53 ` [PATCH 2/7] dccp: Fix sparse warnings Gerrit Renker
2008-06-10 12:53 ` [PATCH 3/7] dccp ccid-2: Bug-Fix - Ack Vectors need to be ignored on request sockets Gerrit Renker
2008-06-10 12:53 ` [PATCH 4/7] dccp ccid-3: TFRC reverse-lookup Bug-Fix Gerrit Renker
2008-06-10 12:53 ` [PATCH 5/7] dccp ccid-3: X truncated due to type conversion Gerrit Renker
2008-06-10 12:53 ` [PATCH 6/7] dccp: Bug in initial acknowledgment number assignment Gerrit Renker
2008-06-10 12:53 ` [PATCH 7/7] dccp: Initialise option area of v4/v6 request socket Gerrit Renker
2008-06-10 14:38 ` Arnaldo Carvalho de Melo
2008-06-10 19:40 ` David Miller
2008-06-10 19:31 ` [PATCH 1/7] dccp ccid-3: Bug-Fix - Zero RTT is possible David Miller
2008-06-10 19:29 ` [Patch 0/7] [dccp]: DCCP bug-fixes for net-2.6 David Miller
2008-06-10 19:32 ` David Miller
2008-06-11 10:36 ` Gerrit Renker [this message]
2008-06-12 1:10 ` [Patch 0/6] [dccp]: DCCP bug-fixes for net-2.6 (revision 01) David Miller
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=20080611103647.GD8403@gerrit.erg.abdn.ac.uk \
--to=gerrit@erg.abdn.ac.uk \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).