ubsec gets stuck after receiving a packet of a particular length

and stops processing any further packets. this is believed to be
a result of the inconsistency of the destination mbuf chain as a
a copy acquired via m_copym2 works fine. so far only one problem
was discovered with the optimized inline version of m_copym2: a
cluster has to be allocated if source chain had one.

unfortunately, this solves the problem only for some packet sizes
so apply a larger hammer and call m_copym2 for now.

the problem was reported and diffs were patiently tested by Joosep
<joosepm-at-gmail-dot-com>, thanks!

deraadt agrees to this temporary measure.

0 files changed, 0 insertions, 0 deletions