PRs for tag 'lagg'
This is an experimental report containing PRs for tag 'lagg' 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 'lagg':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| p | 2014/04/25 | kern/189003 | asomers | [lagg] Page fault in lacp_req() while the lagg is being destroyed |
| o | 2014/01/21 | kern/185967 | net | [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0 |
| o | 2013/09/08 | kern/181931 | net | [vlan] [lagg] vlan over lagg over mlxen crashes the kernel |
| o | 2013/06/19 | kern/179733 | net | [lagg] [patch] interface loses capabilities when protocol changes |
| o | 2013/02/15 | kern/176167 | net | [ipsec][lagg] using lagg and ipsec causes immediate panic |
| o | 2011/07/06 | kern/158694 | net | [ix] [lagg] ix0 is not working within lagg(4) |
| o | 2011/05/19 | kern/157182 | net | [lagg] lagg interface not working together with epair interface on bridge |
| p | 2011/04/30 | kern/156743 | thompsa | [lagg] [patch] if_lagg should not treat vlan-tagged frames as LACP frames |
| o | 2011/04/06 | kern/156226 | net | [lagg]: failover does not announce the failover to switch |
| o | 2010/04/15 | kern/145728 | net | [lagg] Stops working lagg between two servers. |
| f | 2010/01/09 | kern/142518 | net | [em] [lagg] Problem on 8.0-STABLE with em and lagg |
| o | 2009/09/24 | kern/139117 | net | [lagg] + wlan boot timing (EBUSY) |
| o | 2009/07/24 | kern/137089 | net | [lagg] lagg falsely triggers IPv6 duplicate address detection |
| o | 2008/04/30 | kern/123279 | thompsa | [lagg] order of operations dependancy in bringing up lagg interface breaks at-boot configuration |
| o | 2008/04/21 | kern/122954 | net | [lagg] IPv6 EUI64 incorrectly chosen for lagg devices |
| f | 2008/04/15 | kern/122780 | net | [lagg] tcpdump on lagg interface during high pps wedges netcode |
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.