PRs for tag 'bpf'
This is an experimental report containing PRs for tag 'bpf' 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 'bpf':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/08/29 | kern/181657 | net | [bpf] [patch] BPF_COP/BPF_COPX instruction reservation (sync with NetBSD) |
| o | 2012/01/27 | kern/164534 | csjp | [bpf] net.bpf.zerocopy_enable=1 makes pflogd eat cpu and hang |
| o | 2011/12/17 | kern/163370 | csjp | [bpf] [request] enable zero-copy BPF by default |
| o | 2011/07/15 | kern/158930 | net | [bpf] BPF element leak in ifp->bpf_if->bif_dlist |
| f | 2009/08/21 | kern/138029 | net | [bpf] [panic] periodically kernel panic and reboot |
| o | 2009/04/08 | kern/133490 | net | [bpf] [panic] 'kmem_map too small' panic on Dell r900 when bpf_bufsize and bpf_maxbufsize are increased |
| o | 2000/02/10 | kern/16644 | [bpf] [patch] Bad comparison expression in bpf_filter.c |
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.