diff options
| author | 2017-11-28 15:41:01 -0500 | |
|---|---|---|
| committer | 2017-11-30 09:54:27 -0500 | |
| commit | 5492093dc4160d150890bc848c26ba7f8fff3094 (patch) | |
| tree | dc760d6803315b9f62e0b90572c7cb47988b6f56 /net/tipc/msg.c | |
| parent | net: Rearrange dst_entry layout to avoid useless padding. (diff) | |
| download | wireguard-linux-5492093dc4160d150890bc848c26ba7f8fff3094.tar.xz wireguard-linux-5492093dc4160d150890bc848c26ba7f8fff3094.zip | |
xfrm: Stop using dst->next in bundle construction.
While building ipsec bundles, blocks of xfrm dsts are linked together
using dst->next from bottom to the top.
The only thing this is used for is initializing the pmtu values of the
xfrm stack, and for updating the mtu values at xfrm_bundle_ok() time.
The bundle pmtu entries must be processed in this order so that pmtu
values lower in the stack of routes can propagate up to the higher
ones.
Avoid using dst->next by simply maintaining an array of dst pointers
as we already do for the xfrm_state objects when building the bundle.
Signed-off-by: David S. Miller <davem@davemloft.net>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Diffstat (limited to 'net/tipc/msg.c')
0 files changed, 0 insertions, 0 deletions
