The upstream commit message is vague in explaining what was going on,
but I'm gathering there was uninitialized data in a variable that would
trigger the error message? The fix appears to be switching to a static
buffer and initializing it to {0}.
** Description changed:
+ [Impact]
+ Socket failures due to uninitialized memory during name resolution.
+
+ [Test Case]
+ TBD
+
+ [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.
+
+ [Discussion]
+
+
+ [Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135:
unexpected error:
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-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response:
invalid file
-
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135:
unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send:
************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180
***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response:
invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135:
unexpected error:
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.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
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.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804542
Title:
[SRU] Multiple intermittent socket failures during name resolutions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804542/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
