> This is the final fix for the problem Peter reported.
> Turns out most other schedulers get it right, the only other
> case is ingress setting skb->tc_index to the uninitialized
> value of res.classid.
I've applied this and tested prio and rr, and everything is happy again.
Thanks for finding
This is the final fix for the problem Peter reported.
Turns out most other schedulers get it right, the only
other case is ingress setting skb->tc_index to the
uninitialized value of res.classid.
[NET_SCHED]: Fix prio/ingress classification logic error
Fix handling of empty or completely
