This bug was fixed in the package linux - 3.13.0-39.66
---
linux (3.13.0-39.66) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1386629
[ Upstream Kernel Changes ]
* KVM: x86: Check non-canonical addresses upon WRMSR
- LP: #1384539
-
This bug was fixed in the package linux - 3.13.0-39.66
---
linux (3.13.0-39.66) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1386629
[ Upstream Kernel Changes ]
* KVM: x86: Check non-canonical addresses upon WRMSR
- LP: #1384539
-
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
Yes, I can confirm that the trusty-proposed 3.13.0-38 kernel resolves
this issue. The dnsmasq-tftp transfer succeeds in my test environment
without any of the symptoms that were present with the trusty-
updates/security kernels between -30 and -37, nor do I notice any
regressions in my (IPv4) ipvs
@terom-u
Thanks for verifying this fix!
--chris
--
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/1349768
Title:
kernel 3.13.0-32 ipvs IPv6 header not found related to UDP socket
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone
--
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/1349768
Title:
kernel 3.13.0-32 ipvs IPv6 header not found related to UDP
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-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/1349768
Title:
kernel 3.13.0-32 ipvs IPv6 header not found related to UDP
This bug was fixed in the package linux - 3.16.0-18.25
---
linux (3.16.0-18.25) utopic; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1373682
-- Tim Gardner tim.gard...@canonical.com Wed, 24 Sep 2014 19:23:23 -0600
** Changed in: linux (Ubuntu Utopic)
** Description changed:
+ SRU Justificaton:
+
+ [Impact]
+ Users of ipvs may encounter dropped packets and message such as:
+ [70325.516724] IPv6 header not found
+
+ [Fix]
+ Commit eb90b0c734ad793d5f5bf230a9e9a4dcc48df8aa.
+
+ [Regression Potential]
+ This changes NFPROTO_IPV4 to NFPROTO_IPV6
** Changed in: linux (Ubuntu Utopic)
Status: In Progress = Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok patch is upstream in v3.17-rc5:
eb90b0c734ad793d5f5bf230a9e9a4dcc48df8aa
--
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/1349768
Title:
kernel 3.13.0-32 ipvs IPv6 header not found
ACK
3.13.0-35-generic #62~lp1349768v5v201408250842 appears to resolve the
issue completely on my actual test setup as well. No TFTP stalls,
dnsmasq EPERM errors or dmesg errors, and ftrace doesn't show any calls
to ipv6_find_hdr.
--
You received this bug notification because you are a member of
NAK
Unfortunately no, the 3.13.0-35-generic #62~lp1349768v4v201408220857
from above continues to exhibit the same issues with my actual test
setup. Same thing with the ./lp1349768.sh testcase.
The 0041-ipvs-fix-ipv4-issues-in-ip_vs_out.patch in the lp1349768v4
build is a different patch, though?
@terom,
Well, I posted the wrong kernel! I'll post the correct one soon after it
builds. 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/1349768
Title:
kernel 3.13.0-32 ipvs IPv6
This should be the right kernel:
http://people.canonical.com/~arges/lp1349768v5/
I verified it myself and it works, once you verify, I'll go through the SRU
process and get this into Trusty.
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is
@terom
Can you please test the following build:
http://people.canonical.com/~arges/lp1349768v4/
This has the patch identified by upstream; it would be good to have positive
testing on this.
This has VS_IPV6 enabled with the fix:
@terom
Ok, I have an approach here for fixing this here:
http://people.canonical.com/~arges/lp1349768v4/
I'd appreciate any testing on this before I send this upstream. I'll look at
this a bit more to see if I'm missing something.
Thanks,
--
You received this bug notification because you are
E-mail sent upstream about this issue:
http://archive.linuxvirtualserver.org/html/lvs-devel/2014-08/msg00026.html
--
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/1349768
Title:
kernel
NAK
Linux 3.13.0-35-generic #62~lp1349768v3v201408191448 still exhibits the
same symptoms (stalled dnsmasq-tftp transfer and IPv6 header not found
messages). Unloading the ip_vs module clears the issue.
I'll attempt to work out a minimal reproducer.
--
You received this bug notification
Attached is a small script to setup dnsmasq-tftp and ipvs to reproduce
the dnsmasq-tftp stall. The strace at the end should start showing
sendto() = EPERM errors after running the curl tftp://.../ command given
as an example from a remote host.
The exact contents of the ipvs rules don't seem to
@terom
Alright! I've been able to reproduce this issue, I'll start debugging
this today.
Regarding the 3.13.0-34 differences I can look at the patches in that
kernel to see if there was some changes to ipvs or around where that
message shows up.
--
You received this bug notification because
** Tags added: bug-exists-upstream
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is
@terom
Yes, a minimal reproducer would help so I can debug on this end. I really
appreciate your testing and analysis so far. : )
I did setup a quick netboot server using MAAS and it did seem to work; but I
did not do the additional steps of setting up the proper ipvs ruleset to
reproduce the
ACK
I can confirm that this issue is no longer present with the Linux
3.13.0-33-generic #58~lp1349768v2v201407300928 kernel as installed from
above. Rebooting into the given kernel results in dnsmasq-tftp transfers
working fine, and no related dmesg errors occur.
Apologies for the delay. I was
The utopic kernel appears to be affected as well. Booting the same
Ubuntu 14.04 machine into the Linux 3.16.0-6-generic #11-Ubuntu kernel
installed from
https://launchpad.net/ubuntu/+source/linux/3.16.0-6.11/+build/6217368
gives identical symptoms, i.e. dnsmasq-tftp stalls, dmesg reports IPv6
NACK
The same faulty behaviour persists with linux-
image-3.13.0-33-generic=3.13.0-33.58~lp1349768v201407290941 (uname
3.13.0-33-generic #58~lp1349768v201407290941).
I do not notice any difference; identical symptoms. `rmmod ip_vs_rr
ip_vs` continues to immediately resolve the fault.
Note that
I believe this is related to a CONFIG change:
UBUNTU: [Config] Enable CONFIG_IP_VS_IPV6=y
I'm building a 3.13 kernel with this CONFIG reverted I would like you to test
and confirm.
(I'll post a link in a few hours)
In the meantime can you verify if the utopic 3.16 series kernel is also
Ok here is the 3.13 kernel with CONFIG_IP_VS_IPV6=y reverted:
http://people.canonical.com/~arges/lp1349768v2/
Please let me know the results when you can.
In addition, if there is a way to explain a minimal reproducer of this
issue, I could set this up here and run experiments as well.
Thanks,
apport information
** Tags added: apport-collected trusty
** Description changed:
I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
loadbalancer and dnsmasq server for pxebooting servers.
After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that
Reported apport-collect information against package linux-
image-3.13.0-32-generic, reproducing the dnsmasq-tftp issue with a
remote client pxebooting and stalling.
The CurrentDmesg contains the symptom message at 1214.740931
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Trusty)
Status: New = In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee:
@terom:
Can you test the following build:
http://people.canonical.com/~arges/lp1349768/
I've reverted commit: b05f2cbc367eae3ad8de17c65a832fd10e30f4b5 from
ubuntu-trusty which was a backport of
57a7744e09867ebcfa0ccf1d6d529caa7728d552.
Thanks,
--
You received this bug notification because you
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Utopic)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
33 matches
Mail list logo
