Remove the call to M_ASSERTVALID from BPF_MTAP; some mbufs passed to
mpf are allocated on the stack, which causes this check to falsely trigger. A new check which takes on-stack mbufs into account will be reintroduced after 5.2 is out the door. Approved by: re (watson) Requested by: many
This commit is contained in:
parent
e983c8d12d
commit
73c251c926
@ -366,7 +366,6 @@ u_int bpf_filter(const struct bpf_insn *, u_char *, u_int, u_int);
|
||||
bpf_tap((_ifp)->if_bpf, (_pkt), (_pktlen)); \
|
||||
} while (0)
|
||||
#define BPF_MTAP(_ifp,_m) do { \
|
||||
M_ASSERTVALID(_m); \
|
||||
if ((_ifp)->if_bpf) \
|
||||
bpf_mtap((_ifp)->if_bpf, (_m)); \
|
||||
} while (0)
|
||||
|
Loading…
Reference in New Issue
Block a user