From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Roland Franke" <fli4l@franke-prem.de>
Subject: Re: iproute2 4.14.1 tc class add come to kernel-panic
Date: Sat, 3 Feb 2018 08:07:18 +0100
Message-ID: <F1D1A5FA6B1C4F5A96CC0761E5597D60@ROLANDAMD64>
References: <9AD3E60C0FF644D9B0EB7D279E3FE8CC@ROLANDAMD64> <1517238148.3715.88.camel@gmail.com> <1E16D55C93FB425AA8431609B1A38168@ROLANDAMD64> <20180129080024.3ac4e72f@xeon-e3> <CAM_iQpXK4vdNHaKo3pwoXv0EGqZ_eVYC4WKhvd6G-g3RmiMXDA@mail.gmail.com> <CAM_iQpWZxdxmYBJmo-46FOPM22T63MOn9ZCCNfc=VdgcOyktKQ@mail.gmail.com> <C57E419D98164F1C9A1E152D2A3E3699@ROLANDAMD64> <CAM_iQpUh1jzN7otaavAr3jrEDk1KQzOwRhviwxuXhMUSLan-qQ@mail.gmail.com> <992E917AA62349519EA5C7AC46D8AF55@ROLANDAMD64> <CAM_iQpWO5GGC+rfS8G-V7CcX7hnfcyf1n1bQ0CbN2VXZrT5jKQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain;
        format=flowed;
        charset="UTF-8";
        reply-type=original
Content-Transfer-Encoding: 7bit
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
        "Eric Dumazet" <eric.dumazet@gmail.com>,
        "Linux Kernel Network Developers" <netdev@vger.kernel.org>
To: "Cong Wang" <xiyou.wangcong@gmail.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mout.kundenserver.de ([217.72.192.75]:52947 "EHLO
        mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750740AbeBCHHW (ORCPT
        <rfc822;netdev@vger.kernel.org>); Sat, 3 Feb 2018 02:07:22 -0500
In-Reply-To: <CAM_iQpWO5GGC+rfS8G-V7CcX7hnfcyf1n1bQ0CbN2VXZrT5jKQ@mail.gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

Hello,

>> Hello,
>>
>>>>> 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
>>>>
>>
>>> 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