Call NG_SEND_DATA_ONLY under epoch in receive side of ksocket.
This resolves a panic caused by NET_EPOCH_ASSERT under netisr for
callers like ng_ppp.
Fixes: 104827151e2a ("ng_iface: don't recursively enter epoch ...")
Differential D60589
netgraph/ng_ksocket: Enter epoch on NG_SEND_DATA_ONLY Authored by pouria on Sat, Oct 10, 4:28 PM. Tags None Referenced Files
Details
Call NG_SEND_DATA_ONLY under epoch in receive side of ksocket. Fixes: 104827151e2a ("ng_iface: don't recursively enter epoch ...")
Diff Detail
Event TimelineComment Actions Can you please share the trace? I wonder how did we come with ng_ppp not working in the epoch in the first place. Comment Actions This is correct fix, thanks! The commit message should be like this: The work queued by ng_send_fn() is intentionally processed outside of the epoch in ngthread(). It is ng_ksocket's responsibility to enter epoch if it decides to send data from such work. Nothing to do with ng_ppp. Comment Actions Oops, in practice, it was ng_l2tp. I had the panic on mpd5 when my users trying to connect. |