[SRU] Multiple intermittent socket failures during name resolutions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BIND |
Fix Released
|
Undecided
|
Unassigned | ||
bind9 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Lucas Kanashiro |
Bug Description
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
There is no known self contained test case for this bug. However, after the feedback of the bug reporter [1][2] looks the proposed patch is properly fixing the bug.
[1] https:/
[2] https:/
[Regression Potential]
Things to watch for would include memory-related issues and faults relating to long names or addresses. The patch changes memory management for a data buffer used in socket communication. There could be behavioral differences between handling of ipv4 and ipv6 addresses.
[Fix]
See comment #7
This will need to be backported for bionic. Other releases either don't need it or already have it:
bind9 | 1:9.8.1.
bind9 | 1:9.9.5.
bind9 | 1:9.10.
bind9 | 1:9.11.
bind9 | 1:9.11.
bind9 | 1:9.11.
bind9 | 1:9.11.
[Discussion]
[Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../.
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-
Nov 22 09:51:35 mound named[1510]: ../../.
Nov 22 09:51:35 mound named[1510]: internal_send: *******
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 *******
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../.
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.
ProcVersionSign
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.
modified.
mtime.conffile.
mtime.conffile.
Related branches
- Bryce Harrington (community): Approve
- Canonical Server: Pending requested
- Canonical Server Core Reviewers: Pending requested
-
Diff: 345 lines (+323/-0)3 files modifieddebian/changelog (+7/-0)
debian/patches/fix-socket-failures-during-name-resolution.patch (+315/-0)
debian/patches/series (+1/-0)
summary: |
- Multiple intermittent socket failures during name resolutions + [SRU] Multiple intermittent socket failures during name resolutions |
tags: | added: patch |
Changed in bind9 (Ubuntu Bionic): | |
status: | New → Triaged |
importance: | Undecided → Medium |
description: | updated |
Changed in bind9 (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in bind: | |
status: | New → Fix Released |
tags: | added: server-next |
Changed in bind9 (Ubuntu Bionic): | |
assignee: | nobody → Lucas Kanashiro (lucaskanashiro) |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you could then provide steps to reproduce the problem or otherwise explain why you believe this is a bug in Ubuntu rather than a problem specific to your system or network configuration, and then change the bug status back to New.