On Thu, 17 Aug 2023 01:57:59 +0300 Vladimir Oltean wrote: > There are multiple workarounds that can be done in taprio (and mqprio) > depending on what is considered as being sane API. Though I don't want > to get ahead of myself. Maybe there is a way to fast-forward the > qdisc_destroy() of the previous taprio so it doesn't overlap with the > new one's qdisc_create(). Thanks for the details. I'm going to let others comment, but sounds a bit similar to the recent problem with the ingress qdisc. The qdisc expects to own the netdev which explodes when its lifetime rules are fully exercised :(
