From: nuclearcat@nuclearcat.com
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: 4.6.3 kernel panic on ppp interface termination (__tcf_hash_release / spinlock )
Date: Wed, 06 Jul 2016 23:14:22 +0300 [thread overview]
Message-ID: <58100198b6d14f77ce95740e4e912fc3@nuclearcat.com> (raw)
In-Reply-To: <CAM_iQpW0PPZJzhbaeNN1zYZsyopzAWiO1b13XAXZLjpPBKapxQ@mail.gmail.com>
On 2016-07-05 01:02, Cong Wang wrote:
> On Mon, Jul 4, 2016 at 12:07 PM, <nuclearcat@nuclearcat.com> wrote:
>> A little bit more details:
>>
>> ~ # tc -s -d filter show dev ppp0 parent ffff:
>> filter protocol ip pref 100 u32
>> filter protocol ip pref 100 u32 fh 800: ht divisor 1
>> filter protocol ip pref 100 u32 fh 800::1 order 1 key ht 800 bkt 0
>> flowid :1
>> (rule hit 156 success 156)
>> match 00000000/00000000 at 12 (success 156 )
>> action order 1: police 0x1 rate 4024Kbit burst 503000b mtu
>> 2Kb
>> action drop overhead 0b linklayer unspec
>> ref 1 bind 1
>> Action statistics:
>> Sent 10564 bytes 156 pkt (dropped 0, overlimits 0 requeues 0)
>> backlog 0b 0p requeues 0
>>
>>
>> Panic occurs when i delete ingress qdisc
>>
>> tc qdisc del dev ppp0 ingress
>>
>> After reversing commits (and some related commits)
>> 1d4150c02c5709fdfd80f10368a31867de35e72e
>> ddf97ccdd7cb7e00daba465a5c947b8d941dc2a4
>>
>> Problem is not occurring.
>>
>> I'm not certainly sure this commits are causing issue, it is very hard
>> to
>> reverse patches on this particular system.
>>
>
> Can you check if the following commit helps?
>
> commit a03e6fe569713fb3ff0714f8fd7c8785c0ca9e22
> Author: WANG Cong <xiyou.wangcong@gmail.com>
> Date: Mon Jun 6 09:54:30 2016 -0700
>
> act_police: fix a crash during removal
Yes, it fixes issue, thanks.
prev parent reply other threads:[~2016-07-06 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 17:38 4.6.3 kernel panic on ppp interface termination (__tcf_hash_release / spinlock ) nuclearcat
2016-07-04 19:07 ` nuclearcat
2016-07-04 22:02 ` Cong Wang
2016-07-06 20:14 ` nuclearcat [this message]
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=58100198b6d14f77ce95740e4e912fc3@nuclearcat.com \
--to=nuclearcat@nuclearcat.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).