diff options
| author | Ghanan Gowripalan <ghanan@google.com> | 2020-01-15 20:21:20 -0800 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-01-15 20:23:06 -0800 |
| commit | a7a1f00425c6a742a0c953ae3cb6de513011d41b (patch) | |
| tree | 8a38b19941f7c6d3dfac649b00ae3ded37b8bb3d /pkg/seccomp/seccomp_rules.go | |
| parent | 815df2959a76e4a19f5882e40402b9bbca9e70be (diff) | |
Support upgrading expired/removed IPv6 addresses to permanent SLAAC addresses
If a previously added IPv6 address (statically or via SLAAC) was removed, it
would be left in an expired state waiting to be cleaned up if any references to
it were still held. During this time, the same address could be regenerated via
SLAAC, which should be allowed. This change supports this scenario.
When upgrading an endpoint from temporary or permanentExpired to permanent,
respect the new configuration type (static or SLAAC) and deprecated status,
along with the new PrimaryEndpointBehavior (which was already supported).
Test: stack.TestAutoGenAddrAfterRemoval
PiperOrigin-RevId: 289990168
Diffstat (limited to 'pkg/seccomp/seccomp_rules.go')
0 files changed, 0 insertions, 0 deletions