diff options
| author | David Ahern <dsahern@gmail.com> | 2019-10-03 14:46:15 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-10-04 14:31:10 -0700 |
| commit | 8ae72cbf62d2c1879456c0c5872f958e18f53711 (patch) | |
| tree | 25ae03726054fe2b5d77ca5b4dc747fed2845e7f /security | |
| parent | 7a512eb865aa5fcfb396c71047bc9c3b046836b3 (diff) | |
| download | linux-8ae72cbf62d2c1879456c0c5872f958e18f53711.tar.gz linux-8ae72cbf62d2c1879456c0c5872f958e18f53711.tar.bz2 linux-8ae72cbf62d2c1879456c0c5872f958e18f53711.zip | |
Revert "ipv6: Handle race in addrconf_dad_work"
This reverts commit a3ce2a21bb8969ae27917281244fa91bf5f286d7.
Eric reported tests failings with commit. After digging into it,
the bottom line is that the DAD sequence is not to be messed with.
There are too many cases that are expected to proceed regardless
of whether a device is up.
Revert the patch and I will send a different solution for the
problem Rajendra reported.
Signed-off-by: David Ahern <dsahern@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions