Redefine M_FREELIST to be 0x8000; 0x4000 conflicted with two other
uses of m_flags in the kernel. (A future commit will move all private m_flags users here so they're obvious without a great deal of searching.) This should fix the mbuf double-free panics those using ppp or ipfw reset rules have been seeing since the double-free detection code went in.
This commit is contained in:
parent
3a12f5da1f
commit
b9697d572f
@ -153,7 +153,7 @@ struct mbuf {
|
||||
#define M_PROTO3 0x0040 /* protocol-specific */
|
||||
#define M_PROTO4 0x0080 /* protocol-specific */
|
||||
#define M_PROTO5 0x0100 /* protocol-specific */
|
||||
#define M_FREELIST 0x4000 /* mbuf is on the free list */
|
||||
#define M_FREELIST 0x8000 /* mbuf is on the free list */
|
||||
|
||||
/*
|
||||
* mbuf pkthdr flags (also stored in m_flags).
|
||||
|
Loading…
x
Reference in New Issue
Block a user