PRs for tag 'tcp'
This is an experimental report containing PRs for tag 'tcp' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'tcp':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
o | 2014/05/22 | kern/190102 | net | [tcp] net.inet.tcp.drop_synfin=1 no longer works on FreeBSD 10+ [regression] |
p | 2013/11/04 | kern/183659 | net | [tcp] ]TCP stack lock contention with short-lived connections |
o | 2013/09/25 | kern/182382 | net | [tcp] sysctl to set TCP CC method on BIG ENDIAN systems fails |
o | 2013/04/23 | kern/178079 | net | [tcp] Switching TCP CC algorithm panics on sparc64 with a complaint from the MMU |
o | 2013/02/11 | kern/176026 | net | [tcp] [patch] TCP wrappers caused quite a lot of warnings during "make buildworld" |
o | 2013/01/09 | kern/175153 | net | [tcp] will there miss a FIN when do TSO? |
o | 2012/12/30 | kern/174822 | net | [tcp] Page fault in tcp_discardcb under high traffic |
o | 2012/12/18 | kern/174535 | net | [tcp] TCP fast retransmit feature works strange |
o | 2012/12/03 | kern/174087 | andre | [tcp] Problems with ephemeral port selection |
o | 2012/11/02 | kern/173309 | andre | [tcp] TCP connections often prematurely closed by the server side after r242262 [regression] |
o | 2012/06/08 | kern/168842 | andre | [tcp] FreeBSD hosts are sending TCP packets with FIN flag and no ACK set |
o | 2012/03/09 | kern/165879 | andre | [tcp] Syncache syncache.count overflow |
o | 2011/08/15 | kern/159795 | andre | [tcp] excessive duplicate ACKs and TCP session freezes |
o | 2011/08/09 | kern/159621 | net | [tcp] [panic] panic: soabort: so_count |
o | 2011/02/08 | kern/154600 | net | [tcp] [panic] Random kernel panics on tcp_output |
o | 2011/02/06 | kern/154557 | net | [tcp] Freeze tcp-session of the clients, if in the gateway is used quagga |
a | 2010/02/16 | kern/144000 | andre | [tcp] setting TCP_MAXSEG by setsockopt() does not seem to have any effect |
o | 2009/08/21 | kern/138046 | andre | [tcp] tcp sockets stay in SYN_SENT even after receiving RST. never time out as well. |
p | 2008/10/07 | kern/127928 | andre | [tcp] [patch] TCP bandwidth gets squeezed every time tcp_xmit_bandwidth_limit() kicks in |
f | 2008/05/12 | kern/123617 | andre | [tcp] breaking connection when client downloading files from server |
o | 2008/05/12 | kern/123603 | andre | [tcp] tcp_do_segment and Received duplicate SYN |
f | 2008/03/25 | kern/122082 | rwatson | [tcp] NULL pointer dereference in in_pcbdrop |
o | 2008/03/01 | kern/121257 | net | [tcp] TSO + natd -> slow outgoing tcp traffic |
p | 2007/11/12 | kern/118005 | andre | [tcp] Can No Longer SSH into 7.0 host |
a | 2007/09/13 | kern/116335 | andre | [tcp] Excessive TCP window updates |
o | 2007/02/01 | kern/108670 | silby | [tcp] TCP connection ETIMEDOUT |
f | 2006/02/15 | kern/93378 | net | [tcp] Slow data transfer in Postfix and Cyrus IMAP (workaround known) |
o | 2006/02/01 | kern/92690 | silby | [tcp] slowstart_flightsize ignored in 6-STABLE |
o | 2005/10/03 | kern/86871 | net | [tcp] [patch] allocation logic for PCBs in TIME_WAIT state causes packet drops on stateful FWs |
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.