From: "Roland Franke" <fli4l@franke-prem.de>
To: "Cong Wang" <xiyou.wangcong@gmail.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: "Eric Dumazet" <eric.dumazet@gmail.com>,
"Linux Kernel Network Developers" <netdev@vger.kernel.org>
Subject: Re: iproute2 4.14.1 tc class add come to kernel-panic
Date: Tue, 30 Jan 2018 18:46:52 +0100 [thread overview]
Message-ID: <C57E419D98164F1C9A1E152D2A3E3699@ROLANDAMD64> (raw)
In-Reply-To: <CAM_iQpWZxdxmYBJmo-46FOPM22T63MOn9ZCCNfc=VdgcOyktKQ@mail.gmail.com>
Hello,
> On Mon, Jan 29, 2018 at 9:03 AM, Cong Wang <xiyou.wangcong@gmail.com>
> wrote:
>> On Mon, Jan 29, 2018 at 8:00 AM, Stephen Hemminger
>> <stephen@networkplumber.org> wrote:
>>> On Mon, 29 Jan 2018 16:18:07 +0100
>>> "Roland Franke" <fli4l@franke-prem.de> wrote:
>>>
>>>> Hello,
>>>>
>>>> > To: Roland Franke ; netdev@vger.kernel.org
>>>> > Subject: Re: BUG: iproute2 4.14.1 tc class add come to kernel-panic
>>>> >>
>>>> >> tc qdisc add dev eth0 root handle 20: htb default 4 r2q 1
>>>> >> tc class add dev eth0 parent 20: classid 20:7 htb rate 10000kbit
>>>> >> tc qdisc add dev eth0 parent 20:7 sfq perturb 10
>>>> >> tc class add dev eth0 parent 20:7 classid 20:1 htb rate 200kbit ceil
>>>> >> 10000kbit prio 0
>>>> >>
>>>> >> I become an Kernel-panic with the following output:
>>>> >> kern.err kernel: BUG: scheduling while atomic: tc/1036/0x00000200
>>>> >
>>>>
>>>> > Would you have a stack trace to share with us ?
>>>>
>>>> As i will be an absolute newby here, i will not know how to
>>>> get the stack trace out.
>>>> When i will get some information how to get this, i can try to
>>>> give you this information.
>>>> But by my last tests i made the first 3 commands on an console
>>>> and had no error. Only by typing the last line i will get the error and
>>>> here i get actally only the "kern.err kernel: BUG: ....." message.
>>>>
>>>> Roland
>>>
>>> It generates this with lockdep (on 4.15)
>>>
>>> [ 151.355076] HTB: quantum of class 200007 is big. Consider r2q change.
>>
>>
>> We hold qdisc tree spinlock but call rcu_barrier() in
>> mini_qdisc_pair_swap()...
> Well, not min_qdisc things, but it should be resolved by:
> commit efbf78973978b0d25af59bc26c8013a942af6e64
> Author: Cong Wang <xiyou.wangcong@gmail.com>
> Date: Mon Dec 4 10:48:18 2017 -0800
> net_sched: get rid of rcu_barrier() in tcf_block_put_ext()
Against what kernel-version was this be made?
patch from https://patchwork.ozlabs.org/patch/844372/
will not fit against kernel 4.14.15
next prev parent reply other threads:[~2018-01-30 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 14:51 BUG: iproute2 4.14.1 tc class add come to kernel-panic Roland Franke
2018-01-29 15:02 ` Eric Dumazet
2018-01-29 15:18 ` Roland Franke
2018-01-29 16:00 ` Stephen Hemminger
2018-01-29 17:03 ` Cong Wang
2018-01-29 19:07 ` Cong Wang
2018-01-30 17:46 ` Roland Franke [this message]
2018-01-31 6:27 ` Cong Wang
2018-01-31 7:46 ` Roland Franke
2018-02-02 6:42 ` Cong Wang
2018-02-03 7:07 ` Roland Franke
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=C57E419D98164F1C9A1E152D2A3E3699@ROLANDAMD64 \
--to=fli4l@franke-prem.de \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.com \
/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