Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'dummynet'

This is an experimental report containing PRs for tag 'dummynet' 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 'dummynet':
SSubmittedTrackerResp.Description
o2014/05/02kern/189219net[dummynet] [patch] using dummynet on sparc64 and configuring a pipe is an insta-panic
o2012/09/17kern/171711net[dummynet] [panic] Kernel panic in dummynet
o2011/11/14kern/162558net[dummynet] [panic] seldom dummynet panics
f2011/06/12kern/157802net[dummynet] [panic] kernel panic in dummynet
o2011/05/08kern/156877net[dummynet] [panic] dummynet move_pkt() null ptr dereference
s2011/05/02kern/156770melifaro[ipfw] [dummynet] [patch]: performance improvement and several extensions
o2010/02/07kern/143621ipfw[ipfw] [dummynet] [patch] dummynet and vnet use results in panic
o2009/09/15kern/138850net[dummynet] dummynet doesn't work correctly on a bridge
o2009/05/02kern/134157net[dummynet] dummynet loads cpu for 100% and make a system frozen and unstable [regression]
o2009/04/24kern/133969net[dummynet] [panic] Fatal trap 12: page fault while in kernel mode with dummynet
o2009/04/24kern/133968net[dummynet] [panic] dummynet kernel panic
f2007/11/19kern/118128oleg[dummynet] Dummynet cause kernel trap or system freeze
o2006/12/04kern/106316net[dummynet] dummynet with multipass ipfw drops packets when reloading FW
o2005/01/21kern/76539[dummynet] [patch] ipnat + dummynet on output on same interface broken
14 problems total.

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.