Ben Greear <greearb@xxxxxxxxxxxxxxx> writes: > This is from my hacked kernel, could be my fault. I thought the fq > guys might want to know however... Hmm, nothing obvious comes to mind; fq_flow_dequeue() just dequeues a packet from the queue; it only has two memory derefs, to fq->lock and flow->queue. Don't see why either of those should be freed at this point. Unless fq_adjust_removal() is being inlined, perhaps? Then I suppose the flow->tin reference could be the problem, if the txq_info struct was already freed; did you change anything around the handling of TXQs? -Toke
