On 12/27/2017 12:59, Andrey V. Elsukov wrote:
On 27.12.2017 23:09, Navdeep Parhar wrote:
It is not clear to me why it helps. The panic happens on outbound path,
where mbuf should be allocated by network stack and should be writeable.
ip_reass() usually used on inbound path. I think the patch jus
On 27.12.2017 23:09, Navdeep Parhar wrote:
>> It is not clear to me why it helps. The panic happens on outbound path,
>> where mbuf should be allocated by network stack and should be writeable.
>> ip_reass() usually used on inbound path. I think the patch just hides
>> the problem in another place.
On 12/26/2017 03:33, Andrey V. Elsukov wrote:
On 26.12.2017 13:22, Harsh Jain wrote:
panic: m_unshare: m0 0xf80020f82600, m 0xf8005d054100 has M_PKTHDR
cpuid = 15
time = 1495578455
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2c/frame 0xfe044e9bb890
kdb_ba
Julian,
Unfortunately, this issue remains unresolved. I would like to think that
this is just a PEBKAC issue, but I have tried every permutation of escape
characters in case it's an issue with my syntax and I get the same set of
errors. No matter what I do, I can't connect the no match hook of a
John did you get a resolution to this issue?
On 16/12/17 2:59 am, John Lyon wrote:
Harry and Eugene (and others),
I appreciate all of your help. It's been really insightful. Although I
feel like I'm getting much closer to the solution, I don't think my problem
has been diagnosed. I've outlin
