> Modified Files:
>         syssrc/sys/net: bpf.c
> 
> Log Message:
> backout recent changes, for PR 18392.
> bpf_mtap() gets called with not-well-initialized mbuf, so we need to
> go through
> it without touching m->m_pkthdr.len and such.  it's part of our
> bpf_mtap() API (at least today).

Ok, explain to me why we're not fixing the problem of the mbuf being
badly initialised here and instead passing a 'bad mbuf' to bpf_mtap().

If M_PKTHDR is set, then the contents of m_pkthdr are *meant* to be
valid or at least that's what everyone _tells me_ (hi Jason!).

Darren