[Kernel-packages] [Bug 1836261] [NEW] xfrm interface: several kernel panic
Public bug reported: There was several problems reported upstream: 1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823 2/ xfrm interface: avoid corruption on changelink http://patchwork.ozlabs.org/patch/1130240/ 3/ xfrm interface: ifname may be wrong in logs http://patchwork.ozlabs.org/patch/1130241/ 4/ xfrm interface: fix list corruption for x-netns http://patchwork.ozlabs.org/patch/1130385/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836261 Title: xfrm interface: several kernel panic Status in linux package in Ubuntu: New Bug description: There was several problems reported upstream: 1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823 2/ xfrm interface: avoid corruption on changelink http://patchwork.ozlabs.org/patch/1130240/ 3/ xfrm interface: ifname may be wrong in logs http://patchwork.ozlabs.org/patch/1130241/ 4/ xfrm interface: fix list corruption for x-netns http://patchwork.ozlabs.org/patch/1130385/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823725] [NEW] packet: reset network header if packet shorter than ll reserved space
Public bug reported:
After backport of linux upstream commit 9ed988cd5915 ("packet: validate
variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
/ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
is missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
9ed988cd5915 ("packet: validate variable length ll headers")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823725
Title:
packet: reset network header if packet shorter than ll reserved space
Status in linux package in Ubuntu:
Incomplete
Bug description:
After backport of linux upstream commit 9ed988cd5915 ("packet:
validate variable length ll headers")
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
9ed988cd5915 ("packet: validate variable length ll headers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket
** Description changed: + [SRU Justification] + + == Impact == + + IPv6 packets may be dropped during the neighbor resolution when a + userspace program uses IPv6 raw sockets. The commit that introduces + this bug has not been identified, but it's here at least from Xenial (4.4). + This was fixed in the requested backport (from 5.2). + + == Fix == + + Backport the requested patches to Disco (5.0), Bionic (4.15) and + Xenial (4.4). + + == Risk of Regregression == + + The change slightly modifies the target IPv6 address in neighbor + resolution engine. Risk should be low and limited to ipv6. + + --- + With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [SRU Justification] == Impact == IPv6 packets may be dropped during the neighbor resolution when a userspace program uses IPv6 raw sockets. The commit that introduces this bug has not been identified, but it's here at least from Xenial (4.4). This was fixed in the requested backport (from 5.2). == Fix == Backport the requested patches to Disco (5.0), Bionic (4.15) and Xenial (4.4). == Risk of Regregression == The change slightly modifies the target IPv6 address in neighbor resolution engine. Risk should be low and limited to ipv6. --- With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806392] Re: tun/tap: unable to manage carrier state from userland
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806392
Title:
tun/tap: unable to manage carrier state from userland
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
=== SRU Justification ===
[Impact]
Userspace cannot change tun's carrier state.
[Fix]
Add .ndo_change_carrier callback for tun.
[Test]
User confirm the backport works.
[Regression Potential]
Low. It add a new function and a new case switch for ioctl, but the new
code doesn't affect existing behavior.
=== Original Bug Report ===
This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830756] [NEW] tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
Public bug reported:
The upstream commit 2f3ab6221e4c ("tuntap: correctly set SOCKWQ_ASYNC_NOSPACE")
is missing.
Without this patch, userspace apps that use tuntap may be blocked.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830756
Title:
tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
Status in linux package in Ubuntu:
Incomplete
Bug description:
The upstream commit 2f3ab6221e4c ("tuntap: correctly set
SOCKWQ_ASYNC_NOSPACE") is missing.
Without this patch, userspace apps that use tuntap may be blocked.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830756/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823725] Re: packet: reset network header if packet shorter than ll reserved space
This bug is still there, valid packets may be dropped with variable
length protocols like IP tunnels for example. Any actions expected on my
side?
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823725
Title:
packet: reset network header if packet shorter than ll reserved space
Status in linux package in Ubuntu:
New
Bug description:
After backport of linux upstream commit 9ed988cd5915 ("packet:
validate variable length ll headers")
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
9ed988cd5915 ("packet: validate variable length ll headers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
root@ubuntu1604:~# dpkg --list | grep iproute2
ii iproute2 4.3.0-1ubuntu3.16.04.4
amd64networking and traffic control tools
root@ubuntu1604:~# apt-get install iproute2/xenial-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.3.0-1ubuntu3.16.04.5' (Ubuntu:16.04/xenial-proposed
[amd64]) for 'iproute2'
Suggested packages:
iproute2-doc
The following packages will be upgraded:
iproute2
1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
Need to get 523 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 iproute2
amd64 4.3.0-1ubuntu3.16.04.5 [523 kB]
Fetched 523 kB in 0s (6,782 kB/s)
(Reading database ... 85262 files and directories currently installed.)
Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.5_amd64.deb ...
Unpacking iproute2 (4.3.0-1ubuntu3.16.04.5) over (4.3.0-1ubuntu3.16.04.4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up iproute2 (4.3.0-1ubuntu3.16.04.5) ...
root@ubuntu1604:~# dpkg --list | grep iproute2
ii iproute2 4.3.0-1ubuntu3.16.04.5
amd64networking and traffic control tools
root@ubuntu1604:~# ip link add dev dummy0 type dummy
RTNETLINK answers: File exists
root@ubuntu1604:~# ip link add dev dummy1 type dummy
root@ubuntu1604:~# ip link set dev dummy0 up
root@ubuntu1604:~# ip link set dev dummy1 up
root@ubuntu1604:~# tc qdisc add dev dummy0 handle 1: root prio
root@ubuntu1604:~# tc filter add dev dummy0 parent 1: matchall skip_hw action
mirred egress mirror dev dummy1
root@ubuntu1604:~# tc filter show dev dummy0
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
root@ubuntu1604:~#
=> test is OK.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825985] [NEW] macvlan: add ndo_change_proto_down support
Public bug reported:
The following linux upstream patches are missing to support vrrp with
frr:
- b58996795dc4 ("net: dev: add generic protodown handler")
- 2e8b4ba64676 ("macvlan: add ndo_change_proto_down support")
- 8f1af75df3a7 ("vxlan: add ndo_change_proto_down support")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b58996795dc4
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2e8b4ba64676
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f1af75df3a7
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825985
Title:
macvlan: add ndo_change_proto_down support
Status in linux package in Ubuntu:
New
Bug description:
The following linux upstream patches are missing to support vrrp with
frr:
- b58996795dc4 ("net: dev: add generic protodown handler")
- 2e8b4ba64676 ("macvlan: add ndo_change_proto_down support")
- 8f1af75df3a7 ("vxlan: add ndo_change_proto_down support")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b58996795dc4
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2e8b4ba64676
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f1af75df3a7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825985/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830756] Re: tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830756
Title:
tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
Status in linux package in Ubuntu:
Incomplete
Bug description:
The upstream commit 2f3ab6221e4c ("tuntap: correctly set
SOCKWQ_ASYNC_NOSPACE") is missing.
Without this patch, userspace apps that use tuntap may be blocked.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830756/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823725] Re: packet: reset network header if packet shorter than ll reserved space
** Changed in: linux (Ubuntu)
Status: Expired => New
** Description changed:
After backport of linux upstream commit 9ed988cd5915 ("packet: validate
variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
/ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
is missing :
-
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993675a3100b
- 9ed988cd5915 ("packet: validate variable length ll headers")
+ 993675a3100b ("packet: reset network header if packet shorter than ll
+ reserved space")
** Description changed:
- After backport of linux upstream commit 9ed988cd5915 ("packet: validate
- variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
- /ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
- is missing :
+ After backport of linux upstream commit b84bbaf7a6c8 ("packet: in
+ packet_snd start writing at link layer allocation")
+ (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
+ bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
+ missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993675a3100b
993675a3100b ("packet: reset network header if packet shorter than ll
reserved space")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823725
Title:
packet: reset network header if packet shorter than ll reserved space
Status in linux package in Ubuntu:
New
Bug description:
After backport of linux upstream commit b84bbaf7a6c8 ("packet: in
packet_snd start writing at link layer allocation")
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993675a3100b
993675a3100b ("packet: reset network header if packet shorter than ll
reserved space")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881907] [NEW] xfrm interface: fix oops when deleting a x-netns interface
Public bug reported:
[Impact]
When a netns is removed, it may corrupt x-netns xfrm interfaces that
have their link part in this netns. It will later trigger an oops when
those interfaces are removed.
This problem has been fixed in the upstream commit c95c5f58b35e ("xfrm
interface: fix oops when deleting a x-netns interface"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95c5f58b35e
[Test Case]
The steps to reproduce the oops is explained in the commit log of the
upstream patch.
[Regression Potential]
The patch affects only the xfrm interface driver, more precisely, the
deletion part. Thus, the potential regressions are limited to this area.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881907
Title:
xfrm interface: fix oops when deleting a x-netns interface
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
When a netns is removed, it may corrupt x-netns xfrm interfaces that
have their link part in this netns. It will later trigger an oops when
those interfaces are removed.
This problem has been fixed in the upstream commit c95c5f58b35e ("xfrm
interface: fix oops when deleting a x-netns interface"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95c5f58b35e
[Test Case]
The steps to reproduce the oops is explained in the commit log of the
upstream patch.
[Regression Potential]
The patch affects only the xfrm interface driver, more precisely, the
deletion part. Thus, the potential regressions are limited to this
area.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881907/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860969] Re: ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860969
Title:
ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
- 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
- f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
== Fix ==
Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket
Tests are ok here. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] == Impact == IPv6 packets may be dropped during the neighbor resolution when a userspace program uses IPv6 raw sockets. The commit that introduces this bug has not been identified, but it's here at least from Xenial (4.4). This was fixed in the requested backport (from 5.2). == Fix == Backport the requested patches to Disco (5.0), Bionic (4.15) and Xenial (4.4). == Risk of Regregression == The change slightly modifies the target IPv6 address in neighbor resolution engine. Risk should be low and limited to ipv6. --- With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836261] Re: xfrm interface: several kernel panic
root@dut-vm:~# ip netns add foo root@dut-vm:~# ip netns add bar root@dut-vm:~# ip -n foo netns set bar 0 root@dut-vm:~# ip -n foo link add xfrmi0 link-netnsid 0 type xfrm dev lo if_id 23 root@dut-vm:~# ip -n bar link ls xfrmi0 Device "xfrmi0" does not exist. root@dut-vm:~# ip -n foo link ls xfrmi0 2: xfrmi0@if1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/none 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff link-netns bar => interface is correctly created and there is no backtrace in dmesg, OK root@dut-vm:~# ip netns del foo root@dut-vm:~# ip netns del bar root@dut-vm:~# ip link add xfrm1 type xfrm dev lo if_id 1 root@dut-vm:~# ip link add xfrm2 type xfrm dev lo if_id 2 root@dut-vm:~# ip link set xfrm1 type xfrm dev lo if_id 2 RTNETLINK answers: File exists root@dut-vm:~# ip -d link list dev xfrm1 7: xfrm1@lo: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/none 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 1500 xfrm if_id 0x1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 => if_id 0x1 and no backtrace in dmesg, OK root@dut-vm:~# ip link add dummy type dummy root@dut-vm:~# ip link add xfrm1 type xfrm dev dummy if_id 1 root@dut-vm:~# ip l d dummy root@dut-vm:~# ip -d l ls xfrm1 10: xfrm1@if9: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/none 3a:90:dc:59:76:c6 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 1500 xfrm if_id 0x1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 root@dut-vm:~# => no refcnt pb, OK Our internal tests suite is also OK. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836261 Title: xfrm interface: several kernel panic Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1836261 [Impact] Upstream has recently received a number of bug fixes that resolve kernel panics, memory leaks, and list handling for virtual xfrm interfaces that were debuted in 4.19. [Test Case] 3 of the 5 patches have test cases in their commit message for reproducing the fault they address. Another patch prevents including a stale name in the log files. And the other patch that doesn't have an explicit test case improves list handling. [Regression Potential] This patchset contains a nontrivial amount of changes. However, the heavier patches contain test cases that they resolve the regressions they were created for. They've been upstream since July and I don't see any follow up Fixes commits targeting these. The blast radius is "only" the xfrm interface but this is smoke tested and if any dependents rely on it for core functionality they might exercise it and would possibly notice any issues by now as well. Original bug description follows: There was several problems reported upstream: 1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823 2/ xfrm interface: avoid corruption on changelink http://patchwork.ozlabs.org/patch/1130240/ 3/ xfrm interface: ifname may be wrong in logs http://patchwork.ozlabs.org/patch/1130241/ 4/ xfrm interface: fix list corruption for x-netns http://patchwork.ozlabs.org/patch/1130385/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860969] [NEW] ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
Public bug reported:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
- 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
- f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
== Fix ==
Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860969
Title:
ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
Status in linux package in Ubuntu:
New
Bug description:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
- 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
- f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
== Fix ==
Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860986] Re: openvswitch: same tcp session encapsulated with different udp src port for ovs vxlan tunnel
** Description changed:
[SRU Justification]
[Impact]
Packets encapsulated into a vxlan tunnel with openvswitch don't have the
same udp source port for the first packet and the following ones of the
same TCP flow in a DOCKER scenario usecase.
In fact, when using the kernel datapath, the upcall don't include skb
hash info relatived. As VXLAN module uses the skb hash to select UDP src
port, the source port is different for the first packet.
More information can be found here:
https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html
This has been fixed in v5.5 by the following upstream commit:
bd1903b7c4596 ("net: openvswitch: add hash info to upcall")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d
The bug exists since the beginning of vxlan support in openvswitch.
-
+
== Fix ==
-
- Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
+ Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
-
== Risk of Regression ==
This patch only add hash information when we do upcall, thus the risk
should be low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860986
Title:
openvswitch: same tcp session encapsulated with different udp src port
for ovs vxlan tunnel
Status in linux package in Ubuntu:
Incomplete
Bug description:
[SRU Justification]
[Impact]
Packets encapsulated into a vxlan tunnel with openvswitch don't have
the same udp source port for the first packet and the following ones
of the same TCP flow in a DOCKER scenario usecase.
In fact, when using the kernel datapath, the upcall don't include skb
hash info relatived. As VXLAN module uses the skb hash to select UDP
src port, the source port is different for the first packet.
More information can be found here:
https://mail.openvswitch.org/pipermail/ovs-dev/2019-October/364062.html
This has been fixed in v5.5 by the following upstream commit:
bd1903b7c4596 ("net: openvswitch: add hash info to upcall")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch?id=bd1903b7c4596ba6f7677d0dfefd05ba5876707d
The bug exists since the beginning of vxlan support in openvswitch.
== Fix ==
Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch only add hash information when we do upcall, thus the risk
should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860986/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860969] Re: ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
** Description changed:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
- - 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
- - f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
+ - 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
+ - f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
-
== Fix ==
- Backport the requested patches to Focal (5.4), Disco (5.0), Bionic (4.15) and
+ Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860969
Title:
ipsec interfaces: fix sending with bpf_redirect() / AF_PACKET sockets
Status in linux package in Ubuntu:
Incomplete
Bug description:
[SRU Justification]
[Impact]
Packets sent to a vti[6]/xfrm interface via bpf_redirect() or via an
AF_PACKET socket are dropped (no carrier).
This has been fixed in v5.5 by the following upstream commits
- 95224166a903 ("vti[6]: fix packet tx through bpf_redirect()")
- f042365dbffe ("xfrm interface: fix packet tx through bpf_redirect()")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95224166a903
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f042365dbffe
The bug exists since the beginning of each driver.
== Fix ==
Backport the requested patches to Focal (5.4), Eoan (5.3), Bionic (4.15) and
Xenial (4.4).
== Risk of Regression ==
This patch affects only the cases described above (when no dst is
attached to the skb), thus the risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849085] [NEW] netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
Public bug reported: The following upstream patch is missing: - 993e4c929a07 netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849085 Title: netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID Status in linux package in Ubuntu: New Bug description: The following upstream patch is missing: - 993e4c929a07 netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849085] Re: netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
** Description changed:
- The following upstream patch is missing:
+ [SRU Justification]
- - 993e4c929a07 netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
+ [Impact]
+
+ The netlink flag NLM_F_ECHO has no effect with the rtnetlink command
+ RTM_NEWNSID. This has been fixed in v5.4 by the upstream commit
+ 993e4c929a07 ("netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID"). The
+ bug is here since v4.0.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07
+
+ == Fix ==
+
+ Backport the requested patches to Disco (5.0), Bionic (4.15) and
+ Xenial (4.4).
+
+ == Risk of Regregression ==
+
+ This patch is quite trivial and limited to the code that manage
+ RTM_[NEW|GET]NSID commands. Risk should be low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849085
Title:
netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
Status in linux package in Ubuntu:
Incomplete
Bug description:
[SRU Justification]
[Impact]
The netlink flag NLM_F_ECHO has no effect with the rtnetlink command
RTM_NEWNSID. This has been fixed in v5.4 by the upstream commit
993e4c929a07 ("netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID"). The
bug is here since v4.0.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07
== Fix ==
Backport the requested patches to Disco (5.0), Bionic (4.15) and
Xenial (4.4).
== Risk of Regregression ==
This patch is quite trivial and limited to the code that manage
RTM_[NEW|GET]NSID commands. Risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849085/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825985] Re: macvlan: add ndo_change_proto_down support
Can I do something to help?
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825985
Title:
macvlan: add ndo_change_proto_down support
Status in linux package in Ubuntu:
New
Bug description:
The following linux upstream patches are missing to support vrrp with
frr:
- b58996795dc4 ("net: dev: add generic protodown handler")
- 2e8b4ba64676 ("macvlan: add ndo_change_proto_down support")
- 8f1af75df3a7 ("vxlan: add ndo_change_proto_down support")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b58996795dc4
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2e8b4ba64676
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f1af75df3a7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825985/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834465] [NEW] ipv6: fix neighbour resolution with raw socket
Public bug reported: With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: Incomplete Bug description: With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket
Tests are ok for us. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] == Impact == IPv6 packets may be dropped during the neighbor resolution when a userspace program uses IPv6 raw sockets. The commit that introduces this bug has not been identified, but it's here at least from Xenial (4.4). This was fixed in the requested backport (from 5.2). == Fix == Backport the requested patches to Disco (5.0), Bionic (4.15) and Xenial (4.4). == Risk of Regregression == The change slightly modifies the target IPv6 address in neighbor resolution engine. Risk should be low and limited to ipv6. --- With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836261] Re: xfrm interface: several kernel panic
Here are the official commits from Linus tree:
56c5ee1a5823 ("xfrm interface: fix memory leak on creation")
e9e7e85d75f3 ("xfrm interface: avoid corruption on changelink")
e0aaa332e6a9 ("xfrm interface: ifname may be wrong in logs")
c5d1030f2300 ("xfrm interface: fix list corruption for x-netns")
22d6552f827e ("xfrm interface: fix management of phydev")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=56c5ee1a5823
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9e7e85d75f3
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e0aaa332e6a9
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5d1030f2300
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22d6552f827e
The bugs have been introduced in v4.19 by commit f203b76d7809 ("xfrm: Add
virtual xfrm interfaces"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f203b76d7809
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836261
Title:
xfrm interface: several kernel panic
Status in linux package in Ubuntu:
Incomplete
Bug description:
There was several problems reported upstream:
1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823
2/ xfrm interface: avoid corruption on changelink
http://patchwork.ozlabs.org/patch/1130240/
3/ xfrm interface: ifname may be wrong in logs
http://patchwork.ozlabs.org/patch/1130241/
4/ xfrm interface: fix list corruption for x-netns
http://patchwork.ozlabs.org/patch/1130385/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836261/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830756] Re: tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830756
Title:
tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
[SRU Justification]
== Impact ==
1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()") which is part of
kernel v4.5 introduced an issue where userspace processes might not
get notified if a link comes up after initially being down. This was
fixed in the requested backport (from 4.17).
== Fix ==
Backport the requested patch to Bionic (4.15). Xenial (4.4) is not
affected and Disco and later already contain that fix.
== Risk of Regregression ==
The change only slightly modifies a very specific protocol function.
Risk should be low and limited to tuntap.
---
The upstream commit 2f3ab6221e4c ("tuntap: correctly set
SOCKWQ_ASYNC_NOSPACE") is missing.
Without this patch, userspace apps that use tuntap may be blocked.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f3ab6221e4c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830756/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766573] [NEW] linux < 4.11: unable to use netfilter logging from non-init namespaces
Public bug reported: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766573 Title: linux < 4.11: unable to use netfilter logging from non-init namespaces Status in linux package in Ubuntu: Incomplete Bug description: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779830] [NEW] vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Public bug reported:
The following upstream patch (v4.7) is missing in xenial:
450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1779830
Title:
vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Status in linux package in Ubuntu:
New
Bug description:
The following upstream patch (v4.7) is missing in xenial:
450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] [NEW] netns: unable to follow an interface that moves to another netns
Public bug reported:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
Incomplete
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
Hi Joseph,
we also expect to have those commits in xenial.
The test fails with the patched kernel, only IFLA_NEW_NETNSID seems
there.
With the head of the iproute2 (patches to display those attributes have
been merged this week-end):
root@ubuntu1604:~# ./iproute2/ip/ip monitor link&
[1] 859
root@ubuntu1604:~# ip netns add foo
root@ubuntu1604:~# ip l a type dummy
root@ubuntu1604:~# 3: dummy0: mtu 1500 qdisc noop state DOWN
group default
link/ether 5e:cb:ae:4a:69:f8 brd ff:ff:ff:ff:ff:ff
4: dummy1: mtu 1500 qdisc noop state DOWN group default
link/ether 06:de:2b:94:20:78 brd ff:ff:ff:ff:ff:ff
root@ubuntu1604:~# ip l s dummy1 netns foo
Deleted 4: dummy1: mtu 1500 qdisc noop state DOWN group
default
link/ether 06:de:2b:94:20:78 brd ff:ff:ff:ff:ff:ff new-nsid 0
=> only new-nsid is displayed.
With an upstream kernel, you have:
Deleted 5: dummy0: mtu 1500 qdisc noop state DOWN group
default
link/ether 72:33:30:ba:4c:eb brd ff:ff:ff:ff:ff:ff new-nsid 0 new-ifindex 5
'new-ifindex' is also displayed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
The test fails because the attribute IFLA_CARRIER_UP_COUNT and
IFLA_CARRIER_DOWN_COUNT are not declared in this kernel. In this kernel,
IFLA_NEW_IFINDEX has the numeric value of IFLA_CARRIER_UP_COUNT in an upstream
kernel (if I patch iproute2 to use IFLA_CARRIER_UP_COUNT instead of
IFLA_NEW_IFINDEX, I can get the new ifindex).
iproute2 (like a lot of others tools) has a local copy of linux uapi headers,
thus the numeric value of netlink attributes must be the same than upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
It works for me, thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771764] [NEW] iproute2: unable to add ip lwt mpls route on xenial
Public bug reported:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in linux package in Ubuntu:
New
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771764/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771783] [NEW] iproute2: frr route protocols are not converted to string on xenial
Public bug reported:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define their
protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => iproute2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771783
Title:
iproute2: frr route protocols are not converted to string on xenial
Status in iproute2 package in Ubuntu:
New
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Package changed: linux (Ubuntu) => iproute2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Incomplete
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
Any news for the iproute2 part?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
New
Status in linux source package in Xenial:
Fix Released
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642510] Re: sched: clsact qdisc is missing in xenial
Still in progress?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1642510
Title:
sched: clsact qdisc is missing in xenial
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Bug description:
This is implemented in linux v4.5 by the following upstream patch:
1f211a1b929c ("net, sched: add clsact qdisc")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f211a1b929c
The backport is straightforward.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642510/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766573 Title: linux < 4.11: unable to use netfilter logging from non-init namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
I tested the patch, it works.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces
Test is ok on my side. Thank you for the quick fix! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766573 Title: linux < 4.11: unable to use netfilter logging from non-init namespaces Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
Well, it could be a workaround but it would be great to have it in the
4.4 if it's not too complicated for you. What do you think?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
6Wind is requesting these three patches. The patches fix a bug that prevents
a user
from following an interface that moves to another netns.
These commits are also needed in Xenial. However, they will be sent in
a separate SRU request due to additional prereq commits being needed for
Xenial.
== Fixes ==
b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
== Regression Potential ==
Medium due to three patches needed and the changes to core networking.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812875] Re: ip6_gre: fix tunnel list corruption for x-netns
This issue is a kernel panic ...
We reproduce it on ubuntu-18.04 with a third party software
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1812875
Title:
ip6_gre: fix tunnel list corruption for x-netns
Status in linux package in Ubuntu:
Incomplete
Bug description:
The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
("ip6_gre: fix tunnel list corruption for x-netns").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab5098fa25b9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812875/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812875] Re: ip6_gre: fix tunnel list corruption for x-netns
I reported this bug on behalf of a colleague. He is off this week and
will not be able to test this patch before next week.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1812875
Title:
ip6_gre: fix tunnel list corruption for x-netns
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
== SRU Justification ==
Impact: A kernel panic is seen when using some third-party software.
Fix: Upstream commit ab5098fa25b9 ("ip6_gre: fix tunnel list
corruption for x-netns").
Test Case: Confirm that the panic no longer happens with the patch.
Regression Potential: This is a simple fix and suitable for upstream
stable, regressions are unlikely.
---
The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
("ip6_gre: fix tunnel list corruption for x-netns").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab5098fa25b9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812875/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806392] Re: tun/tap: unable to manage carrier state from userland
Any news for this patch?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806392
Title:
tun/tap: unable to manage carrier state from userland
Status in linux package in Ubuntu:
Triaged
Bug description:
This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial
It works on my side:
$ ./ip/ip r a 2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto 188 metric 20
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto 188 metric 20
$ mkdir -p /etc/iproute2/rt_protos.d
$ echo "188 foo" > /etc/iproute2/rt_protos.d/bar.conf
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto foo metric 20
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1771783
Title:
iproute2: frr route protocols are not converted to string on xenial
Status in iproute2 package in Ubuntu:
New
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
> Note that the iproute2 patch will be needed to use this filter:
>
> https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=d5cbf3ff0561
> (embedded headers must be updated also).
This link is dead, here is another one:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=d5cbf3ff0561
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
New
Status in linux source package in Xenial:
Fix Released
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806392] [NEW] tun/tap: unable to manage carrier state from userland
Public bug reported:
This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806392
Title:
tun/tap: unable to manage carrier state from userland
Status in linux package in Ubuntu:
New
Bug description:
This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806392] Re: tun/tap: unable to manage carrier state from userland
Tests are ok on my side, thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806392
Title:
tun/tap: unable to manage carrier state from userland
Status in linux package in Ubuntu:
Triaged
Bug description:
This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774815] Re: Add bpftool to linux-tools-common
Any news on this topic? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774815 Title: Add bpftool to linux-tools-common Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: bpftool is a debugging and introspection tool actively developed by the BPF kernel community. It's developed as part of the kernel source tree under tools/: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/bpf/bpftool It would be really great and appreciated if Ubuntu folks could package this as part of linux-tools-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812875] [NEW] ip6_gre: fix tunnel list corruption for x-netns
Public bug reported:
The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
("ip6_gre: fix tunnel list corruption for x-netns").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab5098fa25b9
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1812875
Title:
ip6_gre: fix tunnel list corruption for x-netns
Status in linux package in Ubuntu:
Incomplete
Bug description:
The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
("ip6_gre: fix tunnel list corruption for x-netns").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab5098fa25b9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812875/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690094] [NEW] linux <3.18: netlink notification is missing when an interface is modified
Public bug reported: The following upstream patches are missing: ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified 90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags 1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated 5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5 There is several ways to reproduce the problem. Here is an example: ip monitor link& ip link set eth1 txqueuelen 18 => no notification ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690094 Title: linux <3.18: netlink notification is missing when an interface is modified Status in linux package in Ubuntu: Incomplete Bug description: The following upstream patches are missing: ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified 90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags 1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated 5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5 There is several ways to reproduce the problem. Here is an example: ip monitor link& ip link set eth1 txqueuelen 18 => no notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894605] [NEW] gtp: unable to associate contextes to interfaces
Public bug reported:
[Impact]
When a user dump pdp contextes, it cannot associate them with existing
gtp interfaces. Thus, the dump is unusable.
This problem has been fixed in the upstream commit b274e47d9e3f ("gtp: add
GTPA_LINK info to msg sent to userspace"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b274e47d9e3f
[Test Case]
Create several gtp interfaces and setup PDP contextes on them. Perform a
dump with the genl command GTP_CMD_GETPDP.
[Regression Potential]
The patch affects only the gtp driver and is quite trivial. Thus, the
potential regressions are limited to this area and low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894605
Title:
gtp: unable to associate contextes to interfaces
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
When a user dump pdp contextes, it cannot associate them with existing
gtp interfaces. Thus, the dump is unusable.
This problem has been fixed in the upstream commit b274e47d9e3f ("gtp: add
GTPA_LINK info to msg sent to userspace"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b274e47d9e3f
[Test Case]
Create several gtp interfaces and setup PDP contextes on them. Perform
a dump with the genl command GTP_CMD_GETPDP.
[Regression Potential]
The patch affects only the gtp driver and is quite trivial. Thus, the
potential regressions are limited to this area and low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894605/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] [NEW] tc/ebpf: unable to use BPF_FUNC_skb_change_head
Public bug reported:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
- This helper exists since linux v4.10, but it cannot be used until the the
upstream commit f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
+ This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
With a newer kernel, the last command succeeds (not output):
root@ubuntu1804hwe:~# uname -a
Linux ubuntu1804hwe 5.9.0-rc3-ge1b81391421b+6wind-net #1 SMP Mon Sep 21
19:31:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1804hwe:~# tc filter add dev dummy1 egress matchall action bpf obj
./test.o sec test
root@ubuntu1804hwe:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
I forget to explain how to check that the tc command was accepted:
root@ubuntu1804hwe:~# tc filter show dev dummy1 egress
filter protocol all pref 49152 matchall chain 0
filter protocol all pref 49152 matchall chain 0 handle 0x1
not_in_hw
action order 1: bpf test.o:[test] id 9 tag 26af4b090d2d67ee jited
default-action pipe
index 1 ref 1 bind 1
root@ubuntu1804hwe:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
Here is an example:
root@ubuntu1804hwe:~# uname -a
Linux ubuntu1804hwe 5.4.0-47-generic #51~18.04.1-Ubuntu SMP Sat Sep 5 14:35:50
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1804hwe:~# cat test.c
#include
#include
#ifndef __section
# define __section(NAME) __attribute__((section(NAME), used))
#endif
static int (*bpf_skb_change_head)(void *ctx, int headroom, int flags) =
(void *) BPF_FUNC_skb_change_head;
__section("test")
int _test(struct __sk_buff *skb)
{
bpf_skb_change_head(skb, 14, 0);
return TC_ACT_OK;
}
char _license[] __section("license") = "GPL";
root@ubuntu1804hwe:~# clang -target bpf -I/usr/include/x86_64-linux-gnu/ -O2 -o
test.o -c test.c
root@ubuntu1804hwe:~# ip link add name dummy1 type dummy
root@ubuntu1804hwe:~# ip link set dummy1 up
root@ubuntu1804hwe:~# tc qdisc add dev dummy1 clsact
root@ubuntu1804hwe:~# tc filter add dev dummy1 egress matchall action bpf obj
./test.o sec test
Prog section 'test' rejected: Invalid argument (22)!
- Type: 4
- Instructions: 5 (0 over limit)
- License: GPL
Verifier analysis:
0: (b7) r2 = 14
1: (b7) r3 = 0
2: (85) call bpf_skb_change_head#43
unknown func bpf_skb_change_head#43
processed 3 insns (limit 100) max_states_per_insn 0 total_states 0
peak_states 0 mark_read 0
Error fetching program/map!
bad action parsing
parse_action: bad value (5:bpf)!
Illegal "action"
root@ubuntu1804hwe:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890796] [NEW] ipsec: policy priority management is broken
Public bug reported:
[Impact]
When the user tries to update the priority field of a SP, the SP is not
updated *AND* a new SP is created. This results to a broken IPsec
configuration.
This problem has been fixed in the upstream commit 4f47e8ab6ab7 ("xfrm: policy:
match with both mark and mask on user interfaces"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f47e8ab6ab7
[Test Case]
root@dut-vm:~# uname -a
Linux dut-vm 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
root@dut-vm:~# ip xfrm policy flush
root@dut-vm:~# ip xfrm policy
root@dut-vm:~# ip xfrm policy add src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp dir
in action allow priority 9 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel
reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~# ip xfrm policy update src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~#
=> Now, there is 2 SP instead of 1.
[Regression Potential]
The patch affects the xfrm stack only. Thus, the potential regressions
are limited to this area.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890796
Title:
ipsec: policy priority management is broken
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
When the user tries to update the priority field of a SP, the SP is
not updated *AND* a new SP is created. This results to a broken IPsec
configuration.
This problem has been fixed in the upstream commit 4f47e8ab6ab7 ("xfrm:
policy: match with both mark and mask on user interfaces"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f47e8ab6ab7
[Test Case]
root@dut-vm:~# uname -a
Linux dut-vm 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
root@dut-vm:~# ip xfrm policy flush
root@dut-vm:~# ip xfrm policy
root@dut-vm:~# ip xfrm policy add src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp dir
in action allow priority 9 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel
reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~# ip xfrm policy update src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~#
=> Now, there is 2 SP instead of 1.
[Regression Potential]
The patch affects the xfrm stack only. Thus, the potential regressions
are limited to this area.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890796/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890796] Re: ipsec: policy priority management is broken
I don't understand which kernel should be tested on xenial. The kernel
4.15.0-112-generic does not have the bug.
** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1890796
Title:
ipsec: policy priority management is broken
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Status in linux-hwe source package in Xenial:
Invalid
Status in linux-oem-5.6 source package in Xenial:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-hwe source package in Bionic:
Fix Committed
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-hwe source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
Confirmed
Bug description:
[Impact]
When the user tries to update the priority field of a SP, the SP is
not updated *AND* a new SP is created. This results to a broken IPsec
configuration.
This problem has been fixed in the upstream commit 4f47e8ab6ab7 ("xfrm:
policy: match with both mark and mask on user interfaces"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f47e8ab6ab7
[Test Case]
root@dut-vm:~# uname -a
Linux dut-vm 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
root@dut-vm:~# ip xfrm policy flush
root@dut-vm:~# ip xfrm policy
root@dut-vm:~# ip xfrm policy add src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp dir
in action allow priority 9 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel
reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~# ip xfrm policy update src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~#
=> Now, there is 2 SP instead of 1.
[Regression Potential]
The patch affects the xfrm stack only. Thus, the potential regressions
are limited to this area.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890796/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Re: tc/ebpf: unable to use BPF_FUNC_skb_change_head
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] [NEW] linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
Public bug reported: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: Incomplete Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
** Summary changed: - linux > 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds + linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: Incomplete Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
Sorry, I just discussed with Thibaut (he has spotted this bug), and I forgot one backport: 3952af4d5034 bonding: add 802.3ad support for 100G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3952af4d5034 This patch has been pushed in kernel 4.5. We only have 100G cards, thus we won't be able to test 5G, 25G and 50G. The patches are straightforward, I'm not sure if it's critical. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
As I explain before, we can only test 100G. It means that the third patch is needed for us to test xenial. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
And you said, you had already backport it :D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
Thibaut will test the xenial kernel next week. Is it ok? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds
Thibaut confirms that the bug is resolved for 100G (xenial). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697892 Title: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: These upstream patches are needed to correctly handle 5G, 25G and 50G speeds in 802.3ad: 19ddde1eeca1 bonding: add 802.3ad support for 25G speeds https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634545] Re: ipv6: connected routes are missing after a down/up cycle on the loopback
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1634545
Title:
ipv6: connected routes are missing after a down/up cycle on the
loopback
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
This upstream patch is missing:
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=a220445f9f4382c36a53d8ef3e08165fa27f7e2c
ipv6: correctly add local routes when lo goes up
The goal of the patch is to fix this scenario:
ip link add dummy1 type dummy
ip link set dummy1 up
ip link set lo down ; ip link set lo up
After that sequence, the local route to the link layer address of dummy1 is
not there anymore.
When the loopback is set down, all local routes are deleted by
addrconf_ifdown()/rt6_ifdown(). At this time, the rt6_info entry still
exists, because the corresponding idev has a reference on it. After the rcu
grace period, dst_rcu_free() is called, and thus ___dst_free(), which will
set obsolete to DST_OBSOLETE_DEAD.
In this case, init_loopback() is called before dst_rcu_free(), thus
obsolete is still sets to something <= 0. So, the function doesn't add the
route again. To avoid that race, let's check the rt6 refcnt instead.
Fixes: 25fb6ca4ed9c ("net IPv6 : Fix broken IPv6 routing table after loopback
down-up")
Fixes: a881ae1f625c ("ipv6: don't call addrconf_dst_alloc again when enable
lo")
Fixes: 33d99113b110 ("ipv6: reallocate addrconf router for ipv6 address when
lo device up")
Reported-by: Francesco Santoro
Reported-by: Samuel Gauthier
CC: Balakumaran Kannan
CC: Maruthi Thotad
CC: Sabrina Dubroca
CC: Hannes Frederic Sowa
CC: Weilong Chen
CC: Gao feng
Signed-off-by: Nicolas Dichtel
Signed-off-by: David S. Miller
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634545/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633404] Re: audit: prevent a new auditd to stop an old auditd still alive
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633404 Title: audit: prevent a new auditd to stop an old auditd still alive Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: The following upstream patch (v4.6) has fixed this problem: audit: stop an old auditd being starved out by a new auditd http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=133e1e5acd4a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633404/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
Note that the iproute2 patch will be needed to use this filter:
https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=d5cbf3ff0561
(embedded headers must be updated also).
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Also affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
New
Status in linux source package in Xenial:
Fix Committed
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690094] Re: linux <3.18: netlink notification is missing when an interface is modified
My tests are ok, thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690094 Title: linux <3.18: netlink notification is missing when an interface is modified Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: The following upstream patches are missing: ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified 90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags 1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated 5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5 There is several ways to reproduce the problem. Here is an example: ip monitor link& ip link set eth1 txqueuelen 18 => no notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662096] Re: ipv6: fix a refcnt leak with peer addr
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662096 Title: ipv6: fix a refcnt leak with peer addr Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: The following upstream patch is missing in ubuntu-14.04: f24062b07dda ipv6: fix a refcnt leak with peer addr http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f24062b07dda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690094] Re: linux <3.18: netlink notification is missing when an interface is modified
What is the plan? Those patches will be applied again when bug #1703401 will be fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690094 Title: linux <3.18: netlink notification is missing when an interface is modified Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: The following upstream patches are missing: ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified 90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags 1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated 5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5 There is several ways to reproduce the problem. Here is an example: ip monitor link& ip link set eth1 txqueuelen 18 => no notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704102] [NEW] bonding: stack dump when unregistering a netdev
Public bug reported:
Here is the reproducer:
ip netns add foo
ip -n foo link add dummy1 type dummy
ip -n foo link add dummy2 type dummy
modprobe bonding
ip -n foo link add bond1 type bond
ip -n foo link set dev bond1 down
ip -n foo addr add 10.10.10.1/24 dev bond1
ip -n foo link set dev bond1 up
ip -n foo link set dummy1 master bond1
ip -n foo link set dummy2 master bond1
ip -n foo link set bond1 mtu 1540
# Move slaves to init_net
ip -n foo link set dummy1 netns 1
ip -n foo link set dummy2 netns 1
# idev are still in netns foo for dummy interfaces:
ip netns exec foo ls /proc/sys/net/ipv4/conf/
ip netns exec foo ls /proc/net/dev_snmp6/
ip netns del foo
dmesg
The bug has been fixed upstream by this patch:
f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when unregistering
slave")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/bonding?id=f51048c3e07b
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704102
Title:
bonding: stack dump when unregistering a netdev
Status in linux package in Ubuntu:
Incomplete
Bug description:
Here is the reproducer:
ip netns add foo
ip -n foo link add dummy1 type dummy
ip -n foo link add dummy2 type dummy
modprobe bonding
ip -n foo link add bond1 type bond
ip -n foo link set dev bond1 down
ip -n foo addr add 10.10.10.1/24 dev bond1
ip -n foo link set dev bond1 up
ip -n foo link set dummy1 master bond1
ip -n foo link set dummy2 master bond1
ip -n foo link set bond1 mtu 1540
# Move slaves to init_net
ip -n foo link set dummy1 netns 1
ip -n foo link set dummy2 netns 1
# idev are still in netns foo for dummy interfaces:
ip netns exec foo ls /proc/sys/net/ipv4/conf/
ip netns exec foo ls /proc/net/dev_snmp6/
ip netns del foo
dmesg
The bug has been fixed upstream by this patch:
f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when
unregistering slave")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/bonding?id=f51048c3e07b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704102] Re: bonding: stack dump when unregistering a netdev
This bug was found on ubuntu 16.04.
I don't reproduce the bug with your Artful kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704102
Title:
bonding: stack dump when unregistering a netdev
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Bug description:
Here is the reproducer:
ip netns add foo
ip -n foo link add dummy1 type dummy
ip -n foo link add dummy2 type dummy
modprobe bonding
ip -n foo link add bond1 type bond
ip -n foo link set dev bond1 down
ip -n foo addr add 10.10.10.1/24 dev bond1
ip -n foo link set dev bond1 up
ip -n foo link set dummy1 master bond1
ip -n foo link set dummy2 master bond1
ip -n foo link set bond1 mtu 1540
# Move slaves to init_net
ip -n foo link set dummy1 netns 1
ip -n foo link set dummy2 netns 1
# idev are still in netns foo for dummy interfaces:
ip netns exec foo ls /proc/sys/net/ipv4/conf/
ip netns exec foo ls /proc/net/dev_snmp6/
ip netns del foo
dmesg
The bug has been fixed upstream by this patch:
f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when
unregistering slave")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/bonding?id=f51048c3e07b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662096] [NEW] ipv6: fix a refcnt leak with peer addr
Public bug reported: The following upstream patch is missing in ubuntu-14.04: f24062b07dda ipv6: fix a refcnt leak with peer addr http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f24062b07dda ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662096 Title: ipv6: fix a refcnt leak with peer addr Status in linux package in Ubuntu: New Bug description: The following upstream patch is missing in ubuntu-14.04: f24062b07dda ipv6: fix a refcnt leak with peer addr http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f24062b07dda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662096] Re: ipv6: fix a refcnt leak with peer addr
There is also two other patches that are needed: - e7478dfc4656 ipv6: use addrconf_get_prefix_route() to remove peer addr - 8e3d5be73681 ipv6: Avoid double dst_free http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e7478dfc4656f http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8e3d5be736810 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662096 Title: ipv6: fix a refcnt leak with peer addr Status in linux package in Ubuntu: Incomplete Bug description: The following upstream patch is missing in ubuntu-14.04: f24062b07dda ipv6: fix a refcnt leak with peer addr http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f24062b07dda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid)
I probably miss something, but I didn't find any new 3.19 kernel in the trusty-proposed repo: $ apt-get install linux-generic-lts-vivid/trusty-proposed linux-headers-generic-lts-vivid/trusty-proposed linux-image-generic-lts-vivid/trusty-proposed Reading package lists... Done Building dependency tree Reading state information... Done E: Release 'trusty-proposed' for 'linux-generic-lts-vivid' was not found E: Release 'trusty-proposed' for 'linux-headers-generic-lts-vivid' was not found E: Release 'trusty-proposed' for 'linux-image-generic-lts-vivid' was not found With 'aptitude -t trusty-proposed' I can see a new 3.13 kernel, but no 3.19. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Status in linux-lts-vivid source package in Trusty: New Status in linux source package in Vivid: Fix Committed Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid)
** Summary changed: - ip6_vti is broken with a kernel 3.19 (vivid) + ip_vti/ip6_vti is broken with a kernel 3.19 (vivid) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid)
> I built a test kernel with a cherry-pick of those three commits. The test > kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1541330 > > Can you test this kernel and see if it resolves this bug? Tests are ok with these packages. Thank you, Nicolas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip_vti/ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541313] Re: kernel panic when umouting rootfs
Tests are ok here. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541313 Title: kernel panic when umouting rootfs Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Bug description: This upstream commit is missing: da362b09e42e umount: Do not allow unmounting rootfs. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e The commit log of this patch explains how to reproduce the kernel panic (see below). Note that this patch depends on 5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8 root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# ./a.out [ 199.274374] [ cut here ] [ 199.274865] kernel BUG at /build/linux-hEVYOL/linux-3.13.0/fs/pnode.c:372! [ 199.275473] invalid opcode: [#1] SMP [ 199.275850] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw nfsd auth_rpcgss parport_pc nfs_acl nfs i2c_piix4 mac_hid lockd sunrpc fscache lp parport psmouse pata_acpi floppy [ 199.276005] CPU: 0 PID: 893 Comm: a.out Not tainted 3.13.0-71-generic #114-Ubuntu [ 199.276005] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.1-0-g4adadbd-20150316_085822-nilsson.home.kraxel.org 04/01/2014 [ 199.276005] task: 88003ba6b000 ti: 88003ad8e000 task.ti: 88003ad8e000 [ 199.276005] RIP: 0010:[] [] propagate_umount+0x143/0x150 [ 199.276005] RSP: 0018:88003ad8fe90 EFLAGS: 00010246 [ 199.276005] RAX: 88003d9b41a0 RBX: 0002 RCX: 88003d9b41a0 [ 199.276005] RDX: RSI: 0002 RDI: 88003ad8fec0 [ 199.276005] RBP: 88003ad8fea8 R08: 88003d9b4190 R09: 88003ad8fec0 [ 199.276005] R10: 811ce392 R11: eae72e00 R12: 88003d9b4140 [ 199.276005] R13: 88003d9b4140 R14: 88003d9b4140 R15: [ 199.276005] FS: 7f72c3f0c740() GS:88003fc0() knlGS: [ 199.276005] CS: 0010 DS: ES: CR0: 80050033 [ 199.276005] CR2: 7f72c3a2d110 CR3: 3d3fd000 CR4: 001407f0 [ 199.276005] DR0: DR1: DR2: [ 199.276005] DR3: DR6: fffe0ff0 DR7: 0400 [ 199.276005] Stack: [ 199.276005] 0002 88003d9b4160 88003e035000 88003ad8fed8 [ 199.276005] 811ddfcc 0002ff9c 88003d9b4140 0002 [ 199.276005] 88003d9b4160 88003ad8ff38 811de9cf 811ce392 [ 199.276005] Call Trace: [ 199.276005] [] umount_tree+0x25c/0x270 [ 199.276005] [] do_umount+0x12f/0x320 [ 199.276005] [] ? final_putname+0x22/0x50 [ 199.276005] [] ? putname+0x29/0x40 [ 199.276005] [] SyS_umount+0x10b/0x120 [ 199.276005] [] system_call_fastpath+0x1a/0x1f [ 199.276005] Code: 50 08 48 89 02 49 89 45 08 e9 57 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 4c 89 e6 4c 89 e7 e8 d5 f6 ff ff 48 89 c3 e9 19 ff ff ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 55 b8 01 [ 199.276005] RIP [] propagate_umount+0x143/0x150 [ 199.276005] RSP [ 199.297648] ---[ end trace 6262a5eb9740f9d0 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
Any news on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1525324 Title: kernel/bonding: wrong netlink messages when deleting a bonding interface Status in linux-lts-trusty package in Ubuntu: New Bug description: Here is the bug: root@ubuntu1404:~# modprobe bonding root@ubuntu1404:~# modprobe dummy root@ubuntu1404:~# ip link set dummy0 master bond0 root@ubuntu1404:~# ip monitor link& [1] 1065 root@ubuntu1404:~# ip link del bond0 Deleted 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff ^C root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# A netlink message advertise that bond0 is deleted and after that two netlink messages are sent telling that bond0 exists again. This bug has been fixed by these upstream commits: 56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88 395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit() http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1525324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541313] [NEW] kernel panic when umouting rootfs
Public bug reported: This upstream commit is missing: da362b09e42e umount: Do not allow unmounting rootfs. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e The commit log of this patch explains how to reproduce the kernel panic (see below). Note that this patch depends on 5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8 root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# ./a.out [ 199.274374] [ cut here ] [ 199.274865] kernel BUG at /build/linux-hEVYOL/linux-3.13.0/fs/pnode.c:372! [ 199.275473] invalid opcode: [#1] SMP [ 199.275850] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw nfsd auth_rpcgss parport_pc nfs_acl nfs i2c_piix4 mac_hid lockd sunrpc fscache lp parport psmouse pata_acpi floppy [ 199.276005] CPU: 0 PID: 893 Comm: a.out Not tainted 3.13.0-71-generic #114-Ubuntu [ 199.276005] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.1-0-g4adadbd-20150316_085822-nilsson.home.kraxel.org 04/01/2014 [ 199.276005] task: 88003ba6b000 ti: 88003ad8e000 task.ti: 88003ad8e000 [ 199.276005] RIP: 0010:[] [] propagate_umount+0x143/0x150 [ 199.276005] RSP: 0018:88003ad8fe90 EFLAGS: 00010246 [ 199.276005] RAX: 88003d9b41a0 RBX: 0002 RCX: 88003d9b41a0 [ 199.276005] RDX: RSI: 0002 RDI: 88003ad8fec0 [ 199.276005] RBP: 88003ad8fea8 R08: 88003d9b4190 R09: 88003ad8fec0 [ 199.276005] R10: 811ce392 R11: eae72e00 R12: 88003d9b4140 [ 199.276005] R13: 88003d9b4140 R14: 88003d9b4140 R15: [ 199.276005] FS: 7f72c3f0c740() GS:88003fc0() knlGS: [ 199.276005] CS: 0010 DS: ES: CR0: 80050033 [ 199.276005] CR2: 7f72c3a2d110 CR3: 3d3fd000 CR4: 001407f0 [ 199.276005] DR0: DR1: DR2: [ 199.276005] DR3: DR6: fffe0ff0 DR7: 0400 [ 199.276005] Stack: [ 199.276005] 0002 88003d9b4160 88003e035000 88003ad8fed8 [ 199.276005] 811ddfcc 0002ff9c 88003d9b4140 0002 [ 199.276005] 88003d9b4160 88003ad8ff38 811de9cf 811ce392 [ 199.276005] Call Trace: [ 199.276005] [] umount_tree+0x25c/0x270 [ 199.276005] [] do_umount+0x12f/0x320 [ 199.276005] [] ? final_putname+0x22/0x50 [ 199.276005] [] ? putname+0x29/0x40 [ 199.276005] [] SyS_umount+0x10b/0x120 [ 199.276005] [] system_call_fastpath+0x1a/0x1f [ 199.276005] Code: 50 08 48 89 02 49 89 45 08 e9 57 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 4c 89 e6 4c 89 e7 e8 d5 f6 ff ff 48 89 c3 e9 19 ff ff ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 55 b8 01 [ 199.276005] RIP [] propagate_umount+0x143/0x150 [ 199.276005] RSP [ 199.297648] ---[ end trace 6262a5eb9740f9d0 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 6wind -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541313 Title: kernel panic when umouting rootfs Status in linux package in Ubuntu: New Bug description: This upstream commit is missing: da362b09e42e umount: Do not allow unmounting rootfs. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e The commit log of this patch explains how to reproduce the kernel panic (see below). Note that this patch depends on 5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8 root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# ./a.out [ 199.274374] [ cut here ] [ 199.274865] kernel BUG at /build/linux-hEVYOL/linux-3.13.0/fs/pnode.c:372! [ 199.275473] invalid opcode: [#1] SMP [ 199.275850] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw nfsd auth_rpcgss parport_pc nfs_acl nfs i2c_piix4 mac_hid lockd sunrpc fscache lp parport psmouse pata_acpi floppy [ 199.276005] CPU: 0 PID: 893 Comm: a.out Not tainted 3.13.0-71-generic #114-Ubuntu [ 199.276005] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.1-0-g4adadbd-20150316_085822-nilsson.home.kraxel.
[Kernel-packages] [Bug 1541330] [NEW] ip_vti6 is broken with a kernel 3.19 (vivid)
Public bug reported: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 6wind -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip_vti6 is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: New Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541313] Re: kernel panic when umouting rootfs
It's a kernel panic, so yes, I'm unable to do anything after the bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541313 Title: kernel panic when umouting rootfs Status in linux package in Ubuntu: Confirmed Bug description: This upstream commit is missing: da362b09e42e umount: Do not allow unmounting rootfs. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e The commit log of this patch explains how to reproduce the kernel panic (see below). Note that this patch depends on 5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8 root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# ./a.out [ 199.274374] [ cut here ] [ 199.274865] kernel BUG at /build/linux-hEVYOL/linux-3.13.0/fs/pnode.c:372! [ 199.275473] invalid opcode: [#1] SMP [ 199.275850] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw nfsd auth_rpcgss parport_pc nfs_acl nfs i2c_piix4 mac_hid lockd sunrpc fscache lp parport psmouse pata_acpi floppy [ 199.276005] CPU: 0 PID: 893 Comm: a.out Not tainted 3.13.0-71-generic #114-Ubuntu [ 199.276005] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.1-0-g4adadbd-20150316_085822-nilsson.home.kraxel.org 04/01/2014 [ 199.276005] task: 88003ba6b000 ti: 88003ad8e000 task.ti: 88003ad8e000 [ 199.276005] RIP: 0010:[] [] propagate_umount+0x143/0x150 [ 199.276005] RSP: 0018:88003ad8fe90 EFLAGS: 00010246 [ 199.276005] RAX: 88003d9b41a0 RBX: 0002 RCX: 88003d9b41a0 [ 199.276005] RDX: RSI: 0002 RDI: 88003ad8fec0 [ 199.276005] RBP: 88003ad8fea8 R08: 88003d9b4190 R09: 88003ad8fec0 [ 199.276005] R10: 811ce392 R11: eae72e00 R12: 88003d9b4140 [ 199.276005] R13: 88003d9b4140 R14: 88003d9b4140 R15: [ 199.276005] FS: 7f72c3f0c740() GS:88003fc0() knlGS: [ 199.276005] CS: 0010 DS: ES: CR0: 80050033 [ 199.276005] CR2: 7f72c3a2d110 CR3: 3d3fd000 CR4: 001407f0 [ 199.276005] DR0: DR1: DR2: [ 199.276005] DR3: DR6: fffe0ff0 DR7: 0400 [ 199.276005] Stack: [ 199.276005] 0002 88003d9b4160 88003e035000 88003ad8fed8 [ 199.276005] 811ddfcc 0002ff9c 88003d9b4140 0002 [ 199.276005] 88003d9b4160 88003ad8ff38 811de9cf 811ce392 [ 199.276005] Call Trace: [ 199.276005] [] umount_tree+0x25c/0x270 [ 199.276005] [] do_umount+0x12f/0x320 [ 199.276005] [] ? final_putname+0x22/0x50 [ 199.276005] [] ? putname+0x29/0x40 [ 199.276005] [] SyS_umount+0x10b/0x120 [ 199.276005] [] system_call_fastpath+0x1a/0x1f [ 199.276005] Code: 50 08 48 89 02 49 89 45 08 e9 57 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 4c 89 e6 4c 89 e7 e8 d5 f6 ff ff 48 89 c3 e9 19 ff ff ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 55 b8 01 [ 199.276005] RIP [] propagate_umount+0x143/0x150 [ 199.276005] RSP [ 199.297648] ---[ end trace 6262a5eb9740f9d0 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip_vti6 is broken with a kernel 3.19 (vivid)
This file is painful to get on a target with no internet access. The exact kernel version is stated in the bug description. Even more, upstream kernel commits and ubuntu kernel commits are listed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip_vti6 is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: Confirmed Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip6_vti is broken with a kernel 3.19 (vivid)
** Summary changed: - ip_vti6 is broken with a kernel 3.19 (vivid) + ip6_vti is broken with a kernel 3.19 (vivid) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: Confirmed Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip6_vti is broken with a kernel 3.19 (vivid)
Yes, it is for that kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541313] Re: kernel panic when umouting rootfs
It does, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541313 Title: kernel panic when umouting rootfs Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: This upstream commit is missing: da362b09e42e umount: Do not allow unmounting rootfs. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e The commit log of this patch explains how to reproduce the kernel panic (see below). Note that this patch depends on 5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8 root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# ./a.out [ 199.274374] [ cut here ] [ 199.274865] kernel BUG at /build/linux-hEVYOL/linux-3.13.0/fs/pnode.c:372! [ 199.275473] invalid opcode: [#1] SMP [ 199.275850] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw nfsd auth_rpcgss parport_pc nfs_acl nfs i2c_piix4 mac_hid lockd sunrpc fscache lp parport psmouse pata_acpi floppy [ 199.276005] CPU: 0 PID: 893 Comm: a.out Not tainted 3.13.0-71-generic #114-Ubuntu [ 199.276005] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.1-0-g4adadbd-20150316_085822-nilsson.home.kraxel.org 04/01/2014 [ 199.276005] task: 88003ba6b000 ti: 88003ad8e000 task.ti: 88003ad8e000 [ 199.276005] RIP: 0010:[] [] propagate_umount+0x143/0x150 [ 199.276005] RSP: 0018:88003ad8fe90 EFLAGS: 00010246 [ 199.276005] RAX: 88003d9b41a0 RBX: 0002 RCX: 88003d9b41a0 [ 199.276005] RDX: RSI: 0002 RDI: 88003ad8fec0 [ 199.276005] RBP: 88003ad8fea8 R08: 88003d9b4190 R09: 88003ad8fec0 [ 199.276005] R10: 811ce392 R11: eae72e00 R12: 88003d9b4140 [ 199.276005] R13: 88003d9b4140 R14: 88003d9b4140 R15: [ 199.276005] FS: 7f72c3f0c740() GS:88003fc0() knlGS: [ 199.276005] CS: 0010 DS: ES: CR0: 80050033 [ 199.276005] CR2: 7f72c3a2d110 CR3: 3d3fd000 CR4: 001407f0 [ 199.276005] DR0: DR1: DR2: [ 199.276005] DR3: DR6: fffe0ff0 DR7: 0400 [ 199.276005] Stack: [ 199.276005] 0002 88003d9b4160 88003e035000 88003ad8fed8 [ 199.276005] 811ddfcc 0002ff9c 88003d9b4140 0002 [ 199.276005] 88003d9b4160 88003ad8ff38 811de9cf 811ce392 [ 199.276005] Call Trace: [ 199.276005] [] umount_tree+0x25c/0x270 [ 199.276005] [] do_umount+0x12f/0x320 [ 199.276005] [] ? final_putname+0x22/0x50 [ 199.276005] [] ? putname+0x29/0x40 [ 199.276005] [] SyS_umount+0x10b/0x120 [ 199.276005] [] system_call_fastpath+0x1a/0x1f [ 199.276005] Code: 50 08 48 89 02 49 89 45 08 e9 57 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 4c 89 e6 4c 89 e7 e8 d5 f6 ff ff 48 89 c3 e9 19 ff ff ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 55 b8 01 [ 199.276005] RIP [] propagate_umount+0x143/0x150 [ 199.276005] RSP [ 199.297648] ---[ end trace 6262a5eb9740f9d0 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
Tests succeeded for us. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525324 Title: kernel/bonding: wrong netlink messages when deleting a bonding interface Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Bug description: Here is the bug: root@ubuntu1404:~# modprobe bonding root@ubuntu1404:~# modprobe dummy root@ubuntu1404:~# ip link set dummy0 master bond0 root@ubuntu1404:~# ip monitor link& [1] 1065 root@ubuntu1404:~# ip link del bond0 Deleted 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff ^C root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# A netlink message advertise that bond0 is deleted and after that two netlink messages are sent telling that bond0 exists again. This bug has been fixed by these upstream commits: 56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88 395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit() http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541330] Re: ip6_vti is broken with a kernel 3.19 (vivid)
I'm off for one week, so I won't be able to test it before Monday the 22th. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541330 Title: ip6_vti is broken with a kernel 3.19 (vivid) Status in linux package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Bug description: $ uname -a Linux ubuntu1404es 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c194f8 ip_vti/ip6_vti: Do not touch skb->mark on xmit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d55c670cbc54 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=049f8e2e28d9 The backport of this upstream patch 213dd74aee76 skbuff: Do not scrub skb mark within the same name space http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=213dd74aee76 in the ubuntu 3.19 kernel has introduced this regression: http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=7525c2de7da1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
I fail to use this tool. The kernel version was provided in the bug description. This bug affects all architectures. The patches needed to fix this issue are also public upstream patches. What kind of information do you need? FYI, here is the screen shot. Note that the browser was successfully launched and the credentials for the applications were ok, but after that, I get a "connection timed out": root@ubuntu1404:~# apport-collect 1525324 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=0wSQ8nk9BZ02dfGL50PV&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press any key to continue or wait (5) seconds... Waiting to hear from Launchpad about your decision... (x-www-browser:4944): Gtk-WARNING **: Could not find the icon 'process-working'. The 'hicolor' theme was not found either, perhaps you need to install it. You can get a copy from: http://icon-theme.freedesktop.org/releases (x-www-browser:4944): Gtk-WARNING **: Error loading theme icon 'stock_new-tab' for stock: Icon 'stock_new-tab' not present in theme (x-www-browser:4944): Gtk-WARNING **: Error loading theme icon 'gtk-add' for stock: Icon 'gtk-add' not present in theme (x-www-browser:4944): Gtk-WARNING **: Error loading theme icon 'bookmark-new' for stock: Icon 'bookmark-new' not present in theme (x-www-browser:4944): Gtk-WARNING **: Error loading theme icon 'stock_add-bookmark' for stock: Icon 'stock_add-bookmark' not present in theme (x-www-browser:4944): Gtk-WARNING **: Error loading theme icon 'gnome- stock-trash' for stock: Icon 'gnome-stock-trash' not present in theme (x-www-browser:4944): Gtk-WARNING **: Error loading theme icon 'gtk- undo-ltr' for stock: Icon 'gtk-undo-ltr' not present in theme (x-www-browser:4944): GLib-CRITICAL **: Source ID 9797 was not found when attempting to remove it ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out You can reset the credentials by removing the file "/root/.cache/apport/launchpad.credentials" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525324 Title: kernel/bonding: wrong netlink messages when deleting a bonding interface Status in linux package in Ubuntu: Incomplete Bug description: Here is the bug: root@ubuntu1404:~# modprobe bonding root@ubuntu1404:~# modprobe dummy root@ubuntu1404:~# ip link set dummy0 master bond0 root@ubuntu1404:~# ip monitor link& [1] 1065 root@ubuntu1404:~# ip link del bond0 Deleted 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff ^C root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# A netlink message advertise that bond0 is deleted and after that two netlink messages are sent telling that bond0 exists again. This bug has been fixed by these upstream commits: 56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88 395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit() http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
Here it is. ** Attachment added: "bug.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+attachment/4553431/+files/bug.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525324 Title: kernel/bonding: wrong netlink messages when deleting a bonding interface Status in linux package in Ubuntu: Incomplete Bug description: Here is the bug: root@ubuntu1404:~# modprobe bonding root@ubuntu1404:~# modprobe dummy root@ubuntu1404:~# ip link set dummy0 master bond0 root@ubuntu1404:~# ip monitor link& [1] 1065 root@ubuntu1404:~# ip link del bond0 Deleted 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff ^C root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# A netlink message advertise that bond0 is deleted and after that two netlink messages are sent telling that bond0 exists again. This bug has been fixed by these upstream commits: 56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88 395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit() http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
Christopher, I just saw that you have removed the tag '6wind'.
I'm not sure how this field should be used, but it was useful to tag bugs
opened by our company with that tag ('6wind') to be able to find them easily.
Is there a way to found all bugs opened by someone and/or a company? For
example all bugs reported by someone with an email that ends with '@6wind.com'?
Thank you,
Nicolas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1525324
Title:
kernel/bonding: wrong netlink messages when deleting a bonding
interface
Status in linux package in Ubuntu:
Triaged
Bug description:
Here is the bug:
root@ubuntu1404:~# modprobe bonding
root@ubuntu1404:~# modprobe dummy
root@ubuntu1404:~# ip link set dummy0 master bond0
root@ubuntu1404:~# ip monitor link&
[1] 1065
root@ubuntu1404:~# ip link del bond0
Deleted 6: bond0: mtu 1500 qdisc noop state DOWN
group default
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
7: dummy0: mtu 1500 qdisc noqueue state
UNKNOWN group default
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN
group default
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
6: bond0: mtu 1500 qdisc noop state DOWN group
default
link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
6: bond0: mtu 1500 qdisc noop state DOWN group
default
root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
7: dummy0: mtu 1500 qdisc noqueue state DOWN group default
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
7: dummy0: mtu 1500 qdisc noqueue state DOWN group default
link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
^C
root@ubuntu1404:~# uname -a
Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1404:~#
A netlink message advertise that bond0 is deleted and after that two
netlink messages are sent telling that bond0 exists again.
This bug has been fixed by these upstream commits:
56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88
395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after
ndo_uninit()
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
Thank you for your quick answer Christopher. In fact, the last link, only shows opened bugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525324 Title: kernel/bonding: wrong netlink messages when deleting a bonding interface Status in linux package in Ubuntu: Triaged Bug description: Here is the bug: root@ubuntu1404:~# modprobe bonding root@ubuntu1404:~# modprobe dummy root@ubuntu1404:~# ip link set dummy0 master bond0 root@ubuntu1404:~# ip monitor link& [1] 1065 root@ubuntu1404:~# ip link del bond0 Deleted 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff ^C root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# A netlink message advertise that bond0 is deleted and after that two netlink messages are sent telling that bond0 exists again. This bug has been fixed by these upstream commits: 56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88 395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit() http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface
> git describe --contains 395eea6ccf2b > v3.19-rc1~118^2~64 > So this bug should not exist in Vivid, Wily or Xenial. Can you confirm that? Kernel >= 3.19 are ok. > I built a Trusty test kernel with these two commits. It can be downloaded > from: > http://kernel.ubuntu.com/~jsalisbury/lp1525324/ > Can you test this kernel and confirm it resolves this bug? If it does, I'll submit a SRU request for those two commits to be added to Trusty. I confirm that this kernel does not have this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525324 Title: kernel/bonding: wrong netlink messages when deleting a bonding interface Status in linux package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux-lts-utopic source package in Trusty: In Progress Bug description: Here is the bug: root@ubuntu1404:~# modprobe bonding root@ubuntu1404:~# modprobe dummy root@ubuntu1404:~# ip link set dummy0 master bond0 root@ubuntu1404:~# ip monitor link& [1] 1065 root@ubuntu1404:~# ip link del bond0 Deleted 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state UNKNOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noop state DOWN group default root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff 7: dummy0: mtu 1500 qdisc noqueue state DOWN group default link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff ^C root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# A netlink message advertise that bond0 is deleted and after that two netlink messages are sent telling that bond0 exists again. This bug has been fixed by these upstream commits: 56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88 395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after ndo_uninit() http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443371] Re: netns: enhance netlink interface for nsid
Here is the list (with the dependencies):
0c7aecd4bde4 netns: add rtnl cmd to add and get peer netns ids
d37512a277df rtnl: add link netns id to interface messages
1728d4fabd1b tunnels: advertise link netns via netlink
317f4810e45e rtnl: allow to create device with IFLA_LINK_NETNSID set
bdef279b993b rtnl: fix error path when adding an iface with a link net
3390e397611c ip6gretap: advertise link netns via netlink
1f17257b1f4a vlan: advertise link netns via netlink
eaca400f1d14 macvlan: advertise link netns via netlink
e5f4e7b9ff33 veth: advertise link netns via netlink
193523bf9373 vxlan: advertise netns of vxlan dev in fdb msg
4967082b4693 vxlan: advertise link netns in fdb messages
33564bbb2cf1 vxlan: setup the right link netns in newlink hdlr
7b4ce694b203 rtnetlink: pass link_net to the newlink handler
06615bed60c1 net: Verify permission to link_net in newlink
cac5e65e8a7e net: do not use rcu in rtnl_dump_ifinfo()
436389007967 net: Handle unregister properly when netdev namespace change fails.
a54acb3a6f85 dev: introduce dev_get_iflink()
ecf2c06a88d2 ip6tnl,gre6,vti6: implement ndo_get_iflink
1e99584b911c ipip,gre,vti,sit: implement ndo_get_iflink
ee9b9596a8dd ipmr,ip6mr: implement ndo_get_iflink
2dbf6b5058ac vlan: implement ndo_get_iflink
ef5fa6bc46ee macvlan: implement ndo_get_iflink
7c4116588b2a ipvlan: implement ndo_get_iflink
5aa7add8f14b infiniband/ipoib: implement ndo_get_iflink
abd2be00d474 dsa: implement ndo_get_iflink
7a66bbc96ce9 net: remove iflink field from struct net_device
e1622baf54df dev: set iflink to 0 for virtual interfaces
a45253bf32bf veth: set iflink to the peer veth
576b7cd2f6ff netns: don't allocate an id for dead netns
b111e4e11123 netns: minor cleanup in rtnl_net_getid()
9a9634545c70 netns: notify netns id events
a143c40c32bb netns: allow to dump netns ids
Note that commit 5aa7add8f14b ("infiniband/ipoib: implement ndo_get_iflink")
needs also this fix (not yet merged):
http://patchwork.ozlabs.org/patch/461764/
The goal of this backport is to be able to identify link netns of
virtual interfaces.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1443371
Title:
netns: enhance netlink interface for nsid
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Precise:
Triaged
Status in linux source package in Trusty:
Triaged
Status in linux source package in Utopic:
Triaged
Status in linux source package in Vivid:
Triaged
Bug description:
The following feature is required to support nsid on netdevices:
http://www.spinics.net/lists/netdev/msg324208.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443371/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593235] [NEW] ovs/gre, vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3
Public bug reported: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 6wind -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Incomplete Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593235] Re: ovs/gre, vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3
apport information ** Tags added: apport-collected ** Description changed: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 16 15:43 seq + crw-rw 1 root audio 116, 33 Jun 16 15:43 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: Error: [Errno 2] No such file or directory + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=vt220 + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/6WIND-hostname ro console=ttyS0,115200n8 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-22-generic N/A + linux-backports-modules-4.4.0-22-generic N/A + linux-firmware1.157 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial xenial xenial + Uname: Linux 4.4.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.5 + dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.5 + dmi.sys.vendor: QEMU ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1593235/+attachment/4684974/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Triaged Status in linux source package in Wily: Triaged Status in linux source package in Xenial: Triaged Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 16 15:43 seq crw-rw 1 root audio 116, 33 Jun 16 15:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/6WIND-hostname ro console=ttyS0,115200n8 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux
[Kernel-packages] [Bug 1593235] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1593235/+attachment/4684981/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Triaged Status in linux source package in Wily: Triaged Status in linux source package in Xenial: Triaged Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 16 15:43 seq crw-rw 1 root audio 116, 33 Jun 16 15:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/6WIND-hostname ro console=ttyS0,115200n8 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593235] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1593235/+attachment/4684977/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Triaged Status in linux source package in Wily: Triaged Status in linux source package in Xenial: Triaged Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 16 15:43 seq crw-rw 1 root audio 116, 33 Jun 16 15:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/6WIND-hostname ro console=ttyS0,115200n8 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593235] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1593235/+attachment/4684978/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593235 Title: ovs/gre,vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3 Status in linux package in Ubuntu: Triaged Status in linux source package in Wily: Triaged Status in linux source package in Xenial: Triaged Bug description: These upstream patches are needed: ovs/gre,geneve: fix error path when creating an iface http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac ovs/vxlan: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6 ovs/gre: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290 ovs/geneve: fix rtnl notifications on iface deletion http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 16 15:43 seq crw-rw 1 root audio 116, 33 Jun 16 15:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/6WIND-hostname ro console=ttyS0,115200n8 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
