Saadia Fatima wrote:
> I observed it in mac layer. Specifically in mac_promisc_dispatch_one. I
> check the original packet to make sure that it is not malformed i.e
> (db_base <= b_rptr <= b_wptr <= db_lim) and MBLKL for original is
> non-zero. Is there any workaround? Is there any address alignmen
I observed it in mac layer. Specifically in mac_promisc_dispatch_one. I check
the original packet to make sure that it is not malformed i.e (db_base <=
b_rptr
<= b_wptr <= db_lim) and MBLKL for original is non-zero. Is there any
workaround? Is there any address alignment or data size factor inv
On 10/22/10 05:32, Paul Durrant wrote:
> MBLKL(mp) is merely the difference between mp->b_wptr and mp->b_rptr,
> which is state usually specific to usage of a particular *instance* of
> a STREAMS message buffer. Such state is not copied across by
> copymsg(). Think of copymsg() as dupmsg() but with
MBLKL(mp) is merely the difference between mp->b_wptr and mp->b_rptr,
which is state usually specific to usage of a particular *instance* of
a STREAMS message buffer. Such state is not copied across by
copymsg(). Think of copymsg() as dupmsg() but with a duplicate dblk_t
rather than a reference to
