On 11-07-15 00:14, Andrew Morton wrote: > > (switched to email. Please respond via emailed reply-to-all, not via > the bugzilla web interface). > > > Here: WARN_ON(next_time == 0); >
>From the other thread on netfilter-devel: > On 11-07-22 11:58, Michal Pokrywka wrote: After bisecting 2.6.39.1 it > turned out that the bug is caused independently by two patches: > > commit b262a5da755cc6ed0cb4fba230cd9bf4037e1096 sch_sfq: fix peek() > implementation > > and > > commit 9df49f2bfe862573911a080c75a6d81113c5c81d sch_sfq: avoid giving > spurious NET_XMIT_CN signals > > Reverting these patches makes HFSC work again. > This one (upstream 8efa885406359af300d46910642b50ca82c0fe47) seems to be the culprit (does reverting only that one cures the problem ?) It allows SFQ to return success on enqueuing, when the packet really replaced some other packet in some other flow. This confuses outer qdisc (in this particular case HFSC) which thinks new packet was actually added each time such situation happes. This in turn causes additional dequeues and ends with attempt to schedule non-existent packets, and triggers the warning. ps. removed netfilter from cc, as it's not really netfilter issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
