New: general protection fault: 0000 [#1] SMP (while using HTB)
Subsystems (2)
Begin forwarded message:
Date: Mon, 14 Jul 2014 04:12:45 -0700
From: "[email protected]" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [Bug 80201] New: general protection fault: 0000 [#1] SMP (while using HTB)
https://bugzilla.kernel.org/show_bug.cgi?id=80201
Bug ID: 80201
Summary: general protection fault: 0000 [#1] SMP (while using
HTB)
Product: Networking
Version: 2.5
Kernel Version: Linux 3.10.41-1.el6.elrepo.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: [email protected]
Reporter: [email protected]
Regression: NoCreated attachment 142971
--> https://bugzilla.kernel.org/attachment.cgi?id=142971&action=edit
Kernel GPF stack trace
Encountered GPF under normal circumstances - no heavy load (CPU, IO, net).
HTB configuration is very simple: 1 HTB class with SFQ qdisc and filter on source port 80:
tc qdisc add dev eth0 root handle 1: htb default 30
tc class add dev eth0 parent 1: classid 1:1 htb rate $LIMIT burst 1500k cburst 1500k
tc qdisc add dev eth0 parent 1:1 handle 10: sfq perturb 10
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip sport 80 0xffff flowid 1:1
Relevant part of vmcore-dmesg.txt attached.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
Quoted 37 lines · Stephen Hemminger
Begin forwarded message:
Date: Mon, 14 Jul 2014 04:12:45 -0700
From: "[email protected]" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [Bug 80201] New: general protection fault: 0000 [#1] SMP (while using HTB)https://bugzilla.kernel.org/show_bug.cgi?id=80201
Bug ID: 80201 Summary: general protection fault: 0000 [#1] SMP (while using HTB) Product: Networking Version: 2.5 Kernel Version: Linux 3.10.41-1.el6.elrepo.x86_64 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Other Assignee: [email protected] Reporter: [email protected] Regression: NoCreated attachment 142971
--> https://bugzilla.kernel.org/attachment.cgi?id=142971&action=edit
Kernel GPF stack traceEncountered GPF under normal circumstances - no heavy load (CPU, IO, net).
HTB configuration is very simple: 1 HTB class with SFQ qdisc and filter on source port 80:
Quoted 9 lines
tc qdisc add dev eth0 root handle 1: htb default 30
tc class add dev eth0 parent 1: classid 1:1 htb rate $LIMIT burst 1500k cburst 1500k
tc qdisc add dev eth0 parent 1:1 handle 10: sfq perturb 10
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip sport 800xffffflowid 1:1Relevant part of vmcore-dmesg.txt attached.
Hmm... the bug seems to be triggered in SFQ, as 'perturb 10' uses a timer.
When sfq_rehash() is called, root qdisc lock is properly held, but sfq_reset() might be called without root qdisc lock being held, via
htb_put() -> htb_destroy_class() -> qdisc_destroy()
race added in commit 225d9b89c937633dfeec502741a174fe0bab5b9f ("sch_sfq: rehash queues in perturb timer")
Not sure how to solve this.
A del_timer_sync() added in sfq_reset() might dead lock, and a del_timer() wont be enough.