Gregory Nutt 0e2986f131 net/tcp: The logic that binds a specific networkd device to a connection was faulty for the case of multiple network devices. On bind(), the local address should be used to associate a device with the connection (if the local address is not INADDR_ANY); On connect(), the remote address should be used (in case the local address is INADDR_ANY). On accept(), it does not matter but the remote address is the one guarenteed to be available.

2015-09-02 19:48:31 -06:00

..

Kconfig

Fix references to the no-longer-existent misc/ directory in comments, README files, and documentation

2015-06-28 08:08:57 -06:00

Make.defs

…

net_chksum.c

net/tcp: The logic that binds a specific networkd device to a connection was faulty for the case of multiple network devices. On bind(), the local address should be used to associate a device with the connection (if the local address is not INADDR_ANY); On connect(), the remote address should be used (in case the local address is INADDR_ANY). On accept(), it does not matter but the remote address is the one guarenteed to be available.

2015-09-02 19:48:31 -06:00

net_dsec2tick.c

…

net_dsec2timeval.c

Suffer the consequences of moving struct timeval to its correct location

2015-02-15 15:18:35 -06:00

net_ipv6_maskcmp.c

…

net_ipv6_pref2mask.c

…

net_lock.c

Networking: Fix some compilation issues noted with network is build with CONFIG_BUILD_KERNEL

2015-07-05 11:18:56 -06:00

net_timeval2dsec.c

Networking: setsockopt() fails when setting timeouts to values less that an 100 msec. That is because the timeout is limited to stops of 1 decisecond and because the conversion of structure timeval was truncating the microsecond remainder. The utility net_timeval2dsec now accespts and option to determin how it handles the remainder: truncate, discarding the remainder, use the remainder to round to the closed decisecond value, or use any non-zero remainder to the next larger whole decisecond value.

2015-05-29 07:17:15 -06:00

utils.h

Networking: The network device list was protected by a re-entrant semaphore. With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state. Of course,those drivers are unable to take the semaphore and will assert.

2015-05-31 08:34:03 -06:00