iproute2 crashes being reported since kernel version 3.13-0-59-generic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
iproute2 (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Trusty |
Invalid
|
High
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
There has recently been a tremendous uptick in the number of crashes being reported about iproute2 since 2015-07-27. This was initially noticed as the phasing of the iproute2 package in -updates for 14.04 (SRU bug 1470091) was stopped. Its worth noting that the same increase in crashes was not detected with the Vivid SRU. Additionally, it appears that the increase in crash rate is unrelated to the iproute2 SRU as it occurs with the version of the package in the release pocket or the updates pocket for 14.04.
The following is a database query showing the quantity of crashes on a daily basis about the iproute2 package for the version of the package in the release pocket and then the updates pocket.
ipdb> old_version
'3.12.0-2'
ipdb> counters_
OrderedDict(
ipdb> new_version
'3.12.0-2ubuntu1'
ipdb> counters_
OrderedDict(
Notice the increase starting on 20150728 for the old version of the package. I've reviewed the individual crashes from 20150729 and all of them (regardless of the iproute2 package version) were using the following kernel version. I'd attribute the drop in crashes on 20150801 and 20150802 to it being the weekend.
3.13.0-59-generic
Unfortunately, all the crashes from the iproute2 package are incomplete / corrupt so there isn't much to go on. Here is one example crash:
https:/
I'll add all the OOPSes from 20150729 as an attachment if somebody wants to have a look at them. I'm also happy to run more queries of the OOPSes to see if we can determine a pattern.
Changed in linux (Ubuntu): | |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: kernel-da-key trusty |
Changed in linux (Ubuntu Trusty): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in iproute2 (Ubuntu): | |
status: | New → Triaged |
Changed in iproute2 (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in iproute2 (Ubuntu): | |
importance: | Undecided → High |
Changed in iproute2 (Ubuntu Trusty): | |
importance: | Undecided → High |
This is the information from ProcCmdline for the crashes on 20150729:
$ grep "^ " 20150729- iproute2- crashes. txt| awk -F, {'print $2'} | sort | uniq -c
1
3 /bin/ip link
59 /sbin/ip route
1 /sbin/ip route show to 0/0
I've tried to manually create a crash using "ip monitor", since it doesn't exit quickly, and the -59- kernel and was able to create a good / complete apport crash.