kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table)

Bug #1514785 reported by Markus Neubauer
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned
Trusty
Fix Released
High
Unassigned
Vivid
Fix Released
High
Unassigned
linux-lts-utopic (Ubuntu)
Invalid
High
Unassigned
Trusty
Fix Released
High
Unassigned

Bug Description

Kernel breaks PBR routing on several versions.
Problem occurs on server and desktop.

Example using linux-image-3.13.0-70

lsb_release:
Ubutu 14.04.3 LTS
Release 14.04

Expected:
To have the normal rule table when using 'ip rule show'
 0: from all lookup local
 32766: from all lookup main
 32767: from all lookup default

Instead:
The 'ip rule show' command is messed up showing lots of repeated rules for local/main/default (did not count them - simply too much)

A sec prob in my case as it is making policy based routing useless if you need to grep whether your rule exists already.

Workaraound, go back to/remain on either of these series:
3.13.0-68
3.16.0.51
3.19.0-33

Confirmed working after the fix (see below messages)
3.13.0-71.114
3.16.0-55.74
3.19.0-39.44

PBR NOT working on:
3.13.0-69
3.13.0-70
3.16.0-52
3.16.0-53
3.19.0-37

description: updated
description: updated
Revision history for this message
Tyler Hicks (tyhicks) wrote :

I have confirmed this bug using linux-image-3.16.0-52-generic

Changed in linux-lts-utopic (Ubuntu):
status: New → Confirmed
information type: Private Security → Public
tags: added: regression-update
Revision history for this message
Norman Henderson (norm-audrey) wrote :

I have the same behavior with 3.16-0-53. The system appears to be working normally in all respects including policy routing, except that the ip rule command produces an infinite loop of 0: from all lookup local. Makes it hard to manage the system... This could be a duplicate of 1516052 which applies to 3.16-0-69.

Revision history for this message
Norman Henderson (norm-audrey) wrote :

Confirmed that booting 3.16-0-51 does not exhibit the problem behavior.

Revision history for this message
Simon Déziel (sdeziel) wrote :

It's not HWE specific as the 3.13 branch is also affected. Here's a recap of the good/bad versions:

3.13.0-68: good
3.13.0-69: bad
3.16.0-51: good
3.16.0-53: bad
3.19.0-32: good
3.19.0-33: good

no longer affects: hwe-next
Revision history for this message
Markus Neubauer (mn-ubuntu) wrote :

3.13.0-70: bad (same failure)

description: updated
Revision history for this message
Michael Fox (news-9) wrote :

I have the same problem in 3.16.0-53. I filed bug #1518715 which may be the same thing.

Revision history for this message
Markus Neubauer (mn-ubuntu) wrote :

seems to be Ubutu specific, as it did not occur on my pure Debian and CentOS systems so far.

description: updated
description: updated
description: updated
description: updated
description: updated
tags: added: kernel-bug
no longer affects: hwe-next
Revision history for this message
Michael Fox (news-9) wrote :

I echo the comments of others that this makes it hard to manage the system. But I'd go further to say it's impossible to manage the system. If we're using rules, we have to be able to see what they are.

Revision history for this message
Michael Fox (news-9) wrote :

As reported in related bug #1518715, "ip rule flush" is also impacted. It appears to hang (never complete).

Revision history for this message
Simon Déziel (sdeziel) wrote :

The broken kernels just made it to -security.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1514785

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
Changed in linux-lts-utopic (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-key
Changed in linux (Ubuntu):
importance: Medium → High
Changed in linux-lts-utopic (Ubuntu):
importance: Medium → High
tags: added: performing-bisect
Changed in linux (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Trusty):
status: New → In Progress
Changed in linux (Ubuntu Vivid):
status: New → In Progress
Changed in linux (Ubuntu Trusty):
importance: Undecided → High
Changed in linux (Ubuntu Vivid):
importance: Undecided → High
Changed in linux (Ubuntu Trusty):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Vivid):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Vivid):
status: In Progress → Confirmed
Changed in linux (Ubuntu Trusty):
status: In Progress → Confirmed
Changed in linux (Ubuntu):
status: In Progress → Confirmed
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu Trusty):
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu Vivid):
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux-lts-utopic (Ubuntu Trusty):
importance: Undecided → High
Changed in linux-lts-utopic (Ubuntu Vivid):
importance: Undecided → High
no longer affects: linux-lts-utopic (Ubuntu Vivid)
no longer affects: linux-lts-utopic (Ubuntu Trusty)
Revision history for this message
Andy Whitcroft (apw) wrote :

This issue was fixed in linux-lts-utopic_3.16.0-55.74~14.04.1.

Changed in linux-lts-utopic (Ubuntu):
status: Confirmed → Invalid
Changed in linux-lts-utopic (Ubuntu Trusty):
importance: Undecided → High
status: New → Fix Released
Luis Henriques (henrix)
Changed in linux (Ubuntu Vivid):
status: Confirmed → Fix Committed
Brad Figg (brad-figg)
tags: added: verification-done-trusty
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.13.0-71.114

---------------
linux (3.13.0-71.114) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1521426

  [ Upstream Kernel Changes ]

  * fib_rules: Fix dump_rules() not to exit early
    - LP: #1514911
    - LP: #1514785

 -- Luis Henriques <email address hidden> Thu, 26 Nov 2015 14:27:35 +0000

Changed in linux (Ubuntu Trusty):
status: Confirmed → Fix Released
status: Confirmed → Fix Released
Revision history for this message
Simon Déziel (sdeziel) wrote :

I can confirm that 3.13.0-71.114 fixes the issue. Thanks

Revision history for this message
Ian! D. Allen (idallen) wrote :

The recent Ubuntu 15.04 kernel update to vmlinuz-3.19.0-37-generic installed this same bug.
I had to reboot back to vmlinuz-3.19.0-33-generic to avoid the loop.

Revision history for this message
Simon Déziel (sdeziel) wrote :

@idallen, try updating to 3.19.0-39.44 which should have the fix. You might need to enable the -proposed repository: https://wiki.ubuntu.com/Testing/EnableProposed

description: updated
description: updated
Revision history for this message
Markus Neubauer (mn-ubuntu) wrote :

I can confirm that 3.19.0-39.44 is ok, too.

description: updated
Revision history for this message
Markus Neubauer (mn-ubuntu) wrote :

I can confirm that 3.16.0-55.74 is ok, too.

description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.19.0-39.44

---------------
linux (3.19.0-39.44) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1521630

  [ Upstream Kernel Changes ]

  * fib_rules: Fix dump_rules() not to exit early
    - LP: #1514785

linux (3.19.0-38.43) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1520641

  [ danielepa ]

  * SAUCE: usb: cdc-acm: blacklist VID/PID 0x058b/0x0041 device
    - LP: #1520147
  * SAUCE: usb: usb-serial-simple: add 0x058b/0x0041 device
    - LP: #1520147

 -- Luis Henriques <email address hidden> Tue, 01 Dec 2015 12:22:47 +0000

Changed in linux (Ubuntu Vivid):
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

You have a regression of this on Linux devstack 3.19.0-37-generic (at least)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.