From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: Cong Wang <cwang@twopensource.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: kernel panic in 4.2.3, rb_erase in sch_fq
Date: Wed, 04 Nov 2015 06:25:29 +0200 [thread overview]
Message-ID: <0705e2b76150c28341d7e1915433450d@visp.net.lb> (raw)
In-Reply-To: <CAHA+R7MNxEkMfyQa56d0HRk2HxeqsduUfM3BkBh=Oxm2yNBVaA@mail.gmail.com>
On 2015-11-04 00:06, Cong Wang wrote:
> On Mon, Nov 2, 2015 at 6:11 AM, Denys Fedoryshchenko
> <nuclearcat@nuclearcat.com> wrote:
>> Hi!
>>
>> Actually seems i was getting this panic for a while (once per week) on
>> loaded pppoe server, but just now was able to get full panic message.
>> After checking commit logs on sch_fq.c i didnt seen any fixes, so
>> probably
>> upgrading to newer kernel wont help?
>
>
> Can you share your `tc qdisc show dev xxxx` with us? And how to
> reproduce
> it? I tried to setup htb+fq and then flip the interface back and forth
> but I don't
> see any crash.
My guess it wont be easy to reproduce, it is happening on box with 4.5k
interfaces, that constantly create/delete interfaces,
and even with that this problem may happen once per day, or may not
happen for 1 week.
Here is script that is being fired after new ppp interface detected. But
pppoe process are independent from
process that are "establishing" shapers.
/sbin/tc qdisc del root
/sbin/tc qdisc add handle 1: root htb default 3
/sbin/tc filter add parent 1:0 protocol ip prio 4 handle 1 fw flowid 1:3
/sbin/tc filter add parent 1:0 protocol ip prio 3 u32 match ip protocol
6 0xff match ip src 10.0.252.8/32 flowid 1:3/sbin/tc filter add parent
1:0 protocol ip prio 5 u32 match ip protocol 1 0xff flowid 1:0
/sbin/tc filter add parent 1:0 protocol ip prio 5 u32 match ip protocol
6 0xff match ip sport 80 0xffff flowid 1:4
/sbin/tc filter add parent 1:0 protocol ip prio 5 u32 match ip protocol
6 0xff match ip sport 443 0xffff flowid 1:5
/sbin/tc filter add parent 1:0 protocol ip prio 100 u32 match u32 0 0
flowid 1:2
/sbin/tc class add classid 1:1 parent 1:0 htb rate 512Kbit ceil
512Kbit.
/sbin/tc class add classid 1:2 parent 1:1 htb rate 32Kbit ceil 512Kbit
/sbin/tc class add classid 1:3 parent 1:0 htb rate 10Mbit ceil 10Mbit
/sbin/tc class add classid 1:4 parent 1:1 htb rate 32Kbit ceil 512Kbit
/sbin/tc class add classid 1:5 parent 1:1 htb rate 32Kbit ceil 512Kbit
/sbin/tc qdisc add parent 1:2 fq limit 300
/sbin/tc qdisc add parent 1:3 pfifo limit 300
/sbin/tc qdisc add parent 1:4 fq limit 300
/sbin/tc qdisc add parent 1:5 fq limit 300
Possible cases come to my mind (but maybe i missed others):
Script and tc working and interface are deleted in a process (e.g.
interface disappears)
Script deleting root while there is heavy traffic on interface and a
lot of packets queued
ppp interface destroyed, while there is a lot of traffic queued on it
(this one a bit rare situation)
>
> Thanks.
next prev parent reply other threads:[~2015-11-04 4:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 14:11 Denys Fedoryshchenko
2015-11-02 15:24 ` Eric Dumazet
2015-11-02 15:58 ` Denys Fedoryshchenko
2015-11-02 16:12 ` Eric Dumazet
2015-11-02 16:21 ` Denys Fedoryshchenko
2015-11-03 22:06 ` Cong Wang
2015-11-04 4:25 ` Denys Fedoryshchenko [this message]
2015-11-04 4:46 ` Eric Dumazet
2015-11-04 4:58 ` Eric Dumazet
2015-11-04 5:13 ` Denys Fedoryshchenko
2015-11-13 21:41 ` Denys Fedoryshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0705e2b76150c28341d7e1915433450d@visp.net.lb \
--to=nuclearcat@nuclearcat.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®