[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM_iQpXM9jBmq5y5RZ+Gb02v44sjAN6thxuO6jiHg+6rgo+4sg@mail.gmail.com>
Date: Thu, 2 Nov 2017 17:15:32 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Dave Taht <dave.taht@...il.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Oops with HTB on net-next
On Thu, Nov 2, 2017 at 4:34 PM, Dave Taht <dave.taht@...il.com> wrote:
> On Thu, Nov 2, 2017 at 11:09 AM, Cong Wang <xiyou.wangcong@...il.com> wrote:
>> On Wed, Nov 1, 2017 at 1:17 PM, Dave Taht <dave.taht@...il.com> wrote:
>>>
>>> That is not in net-next, and the "net" version of that one patch does
>>> not apply to net-next. The relevant thread says "... another fun merge
>>> into net-next".
>>>
>>> Please let me know when the fun is done, and I'll retest.
>>
>> -net is merged into -net-next now.
>
> retested with net-next as of commit: 2d2faaf0568b4946d9abeb4e541227b4ca259840
>
> Run after boot, with the system fairly idle, sqm-scripts works in
> setting up htb, fq_codel, filters, iptables rules, etc.
>
> If I run sqm-scripts in early boot, (run out of
> /etc/network/if-up.d/sqm) with all the other stuff going on then, it
> still fails.
>
> sqm does lots of complicated stuff in rapid succession, and I'm not
> sure how to go about reproducing this more simply than saying grab
> those, and hand them conf files for one existing and one non-existing
> device.
>
> I'll try to make it happen at later times, and try ripping out (for
> example) the ifb setup and tc_mirred, etc, for the early boot
> scenario. Can you suggest other means of debugging?
Ah, I know what's the bug now... Sending the patch now...
Powered by blists - more mailing lists