3.13.0-71: IPv6 UDP DNS packets are not received
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Kamal Mostafa | ||
Trusty |
Fix Released
|
Undecided
|
Kamal Mostafa | ||
Vivid |
Fix Released
|
Undecided
|
Kamal Mostafa | ||
Wily |
Fix Released
|
Undecided
|
Kamal Mostafa | ||
Xenial |
Fix Released
|
High
|
Kamal Mostafa | ||
linux-lts-trusty (Ubuntu) |
Invalid
|
High
|
Kamal Mostafa | ||
Precise |
Fix Released
|
Undecided
|
Kamal Mostafa | ||
linux-lts-utopic (Ubuntu) |
Fix Released
|
Undecided
|
Kamal Mostafa |
Bug Description
After upgrading linux kernel from version 3.13.0-68 to 3.13.0-71 then Kopete (IM messenger) stopped working, cannot connect to any jabber server.
I started debugging this problem and found out that, problem resolve when I boot back 3.13.0-68 kernel version (without touching any system files or packages). When I boot 3.13.0-71 Kopete always does not connect.
Next I debugged that problem on 3.13.0-71 is just when /etc/resolv.conf contains only IPv6 addresses of DNS servers.
Problem is comes down to dns resolver (jabber in Kopete has its own for SRV records) and syscall recvfrom() (on IPv6 socket) always return error -EAGAIN without any data returned. But wireshark see that DNS response was recevied.
So it looks like that after 3.13.0-68 kernel was included some change which broke receiving UDP packets via IPv6 socket. IPv4 is OK.
tags: | added: kernel-da-key |
Changed in linux-lts-trusty (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: per |
tags: |
added: performing-bisect removed: per |
tags: | added: regression-update trusty |
no longer affects: | linux-lts-trusty (Ubuntu Trusty) |
no longer affects: | linux-lts-trusty (Ubuntu Vivid) |
no longer affects: | linux-lts-trusty (Ubuntu Wily) |
no longer affects: | linux-lts-trusty (Ubuntu Xenial) |
no longer affects: | linux (Ubuntu Precise) |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Wily): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Vivid): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Trusty): | |
status: | New → Fix Committed |
Changed in linux-lts-utopic (Ubuntu): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Trusty): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux (Ubuntu Vivid): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux (Ubuntu Wily): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux-lts-trusty (Ubuntu Precise): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux-lts-utopic (Ubuntu): | |
assignee: | nobody → Kamal Mostafa (kamalmostafa) |
Changed in linux-lts-trusty (Ubuntu Precise): | |
status: | New → In Progress |
Changed in linux-lts-trusty (Ubuntu): | |
status: | In Progress → Invalid |
Hi Pali,
I'd like to try and reproduce this bug. Can you list the steps I would need to perform to reproduce the bug? Would it just be to use the Kopete client and try to connect to a jabber server?
Also, do I need to do some network reconfiguration? I am currently using IPv4, and do not have IPv6 configured.
I'm also going to build a test kernel for you to try with the following three commits reverted: and_csum_ datagram_ iov
538c22c net/ipv6: Correct PIM6 mrt_lock handling
483d538 [stable-only] net: add length argument to skb_copy_
16b7201 ipv6: fix exthdrs offload registration in out_rt path
If that does not fix the issue, we can perform a kernel bisect to identify the exact commit that introduced the regression.