moby--moby/libnetwork/drivers
Madhu Venugopal 6901ea51dc Prefer Netlink calls over ioctl
As seen in https://github.com/docker/docker/issues/14738 there is
general instability in the later kernels under race conditions when ioctl
calls are used in parallel with netlink calls for various operations.
(We are yet to narrow down to the exact root-cause on the kernel).

For those older kernels which doesnt support some of the netlink APIs,
we can fallback to using ioctl calls. Hence bringing back the original
code that used netlink (https://github.com/docker/libnetwork/pull/349).

Also, there was an existing bug in bridge creation using netlink which
was setting bridge mac during bridge creation. That operation is not
supported in the netlink library (and doesnt throw an error either).
Included a fix for that condition by setting the bridge mac after
creating the bridge.

Signed-off-by: Madhu Venugopal <madhu@docker.com>
2015-07-30 09:10:22 -07:00
..
bridge Prefer Netlink calls over ioctl 2015-07-30 09:10:22 -07:00
host Honor driver side resolv.conf file 2015-07-02 10:39:06 -07:00
null Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00
overlay Sometimes fdb points to wrong vtep 2015-07-20 18:01:40 -07:00
remote Expose the remote driver API structs publicly. 2015-07-16 06:11:50 +00:00
windows Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00