netdev - Re: iproute2 4.14.1 tc class add come to kernel-panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <F1D1A5FA6B1C4F5A96CC0761E5597D60@ROLANDAMD64>
Date:   Sat, 3 Feb 2018 08:07:18 +0100
From:   "Roland Franke" <fli4l@...nke-prem.de>
To:     "Cong Wang" <xiyou.wangcong@...il.com>
Cc:     "Stephen Hemminger" <stephen@...workplumber.org>,
        "Eric Dumazet" <eric.dumazet@...il.com>,
        "Linux Kernel Network Developers" <netdev@...r.kernel.org>
Subject: Re: iproute2 4.14.1 tc class add come to kernel-panic

Hello,

>> Hello,
>>
>>>>> Well, not min_qdisc things, but it should be resolved by:
>>>>
>>>>
>>>>> commit efbf78973978b0d25af59bc26c8013a942af6e64
>>>>> Author: Cong Wang <xiyou.wangcong@...il.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
>>>>
>>
>>> It is merged during 4.15 window, it was to address a performance
>>> issue, I don't realize it fixes any bug until you report this.
>>
>>
>>> If you need, we can ask DaveM to queue it for stable, but it may
>>> need some other commit too.
>>
>>
>> It is not for me. It is a general question, if tc schould work with
>> the requested function general not with the kernel-line 4.14 (As
>> i was thinking that this should be come to a very long support.
>> (As i was suggest to read in an german page for computers; but
>> it may be a mistake from my side)
>> Or if the 4.14 series come to a "short end" and then it take no
>> matter when the function not work.
>>
>
> Sure, I will send a list of commits to backport to DaveM.
>
Only as information:
With Kernel 4.15(.0) i will get the same problem here by me.
At last: 
kern.err kernel: BUG: scheduling while atomic: tc/23022/0x00000200

Best regards,
Roland