This bug was fixed in the package linux - 4.13.0-17.20
---
linux (4.13.0-17.20) artful; urgency=low
* linux: 4.13.0-17.20 -proposed tracker (LP: #1728927)
[ Seth Forshee ]
* thunderx2 ahci errata workaround needs additional delays (LP: #1724117)
- SAUCE: ahci: thunderx2:
This bug was fixed in the package linux - 4.13.0-17.20
---
linux (4.13.0-17.20) artful; urgency=low
* linux: 4.13.0-17.20 -proposed tracker (LP: #1728927)
[ Seth Forshee ]
* thunderx2 ahci errata workaround needs additional delays (LP: #1724117)
- SAUCE: ahci: thunderx2:
Since on 8th Nov you wrote "in 5 days or it will be dropped" (I verified
and it was good) I expected a fix to be released already.
Not super important, but can you share an ETA on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Waiting on the kernel fix to fully release, but as we won't change
libvirt updating the task.
** Changed in: libvirt (Ubuntu Artful)
Status: Confirmed => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you
Test from [2] in c #8.
4.13.0-16-generic
gcc bind-collision.c && ./a.out
bind: Address already in use
AF_INET check failed.
$ gcc -D CHECK_IPV6 bind-collision.c && ./a.out
AF_INET6 success
AF_INET success
$ gcc bind-collision.c && ./a.out
AF_INET success
>From proposed:
4.13.0-17-generic
$ gcc
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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Artful)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722702
** Changed in: linux (Ubuntu Artful)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722702
Title:
libvirt - vnc port selection regression with newer kernels
To
** Also affects: libvirt (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Bug appears in linux-image-4.11.x kernels on 16.04.3.
+ SRU Justification:
+
+ Impact: Bug appears in linux-image-4.11.x kernels on 16.04.3.
4.8.x and 4.10.x are okay.
When libvirtd is restarted on Kernel 4.11.0-x-generic or above , it
loses all information
@smb - Yes that is the correct summary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722702
Title:
libvirt - vnc port selection regression with newer kernels
To manage notifications about this
>From the comments I conclude that the following three patches from Linux
tree need to be picked:
cbb2fb5 net: set tb->fast_sk_family
7a56673 net: use inet6_rcv_saddr to compare sockets
fbed24b inet: fix improper empty comparison
Patches fix: 637bc8bbe6c0 ("inet: reset tb->fastreuseport when
Pinged the kernel team (smb) to take a look as I'd be scared of this and
further consequences of the regression when Xenial HWE kernels and
Artful will be released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is no apport collect needed, this is known upstream and applies to
all >=4.11 - fix is in 4.14-rc2 but should be part of 4.13 on release to
avoid regressions in more programs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: libvirt (Ubuntu)
I'd ask the kernel Team to integrate the following changes into our 4.13 kernel
release to avoid any sort of update-regressions related to SO_REUSEPORT [1]
- Reproducer [2] without libvirt, how to use in [3]
- Fixes are submitted as [3] - [6]
- If I tracked them correctly they went upstream
Thanks Daniel,
after discussing shortly on IRC and checking all the references together:
- https://www.redhat.com/archives/libvir-list/2017-September/msg00519.html
- https://bugzilla.redhat.com/show_bug.cgi?id=1432684
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863266
-
This is almost certainly the kernel bug mentioned in that Fedora BZ.
There is however a workaround added in libvirt now for distros/users
who can't fix their kernel https://www.redhat.com/archives/libvir-
list/2017-September/msg00519.html
--
You received this bug notification because you are a
Duping my bug (with the failed repro) onto this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722702
Title:
libvirt - vnc port selection regression with newer kernels
To manage notifications
18 matches
Mail list logo
