kernel-packages team mailing list archive

[Markus Neubauer <mn-ubuntu@xxxxxxxxxxxxxxxx>]

** Description changed:

- Host ist kvm
- 
- Within KVM guest using ubuntu server when using these kernels on
+ PBR routing is broken using some kernel versions. Problem occurs on KVM
+ guests and Desktop.
  
  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
+  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)
  It seems like it stucks within a loop adding/displaying and adding/displaying... but the system is not blocked.
- A sec prob in my case as it is making policy based routing useless if you need to grep whether your rule exists already. 
+ 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:
  I went back to the 3.16.0.51 series.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1514785

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

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  PBR routing is broken using some kernel versions. Problem occurs on
  KVM guests and Desktop.

  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)
  It seems like it stucks within a loop adding/displaying and adding/displaying... but the system is not blocked.
  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:
  I went back to the 3.16.0.51 series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1514785/+subscriptions