diff options
author | Taehee Yoo <ap420073@gmail.com> | 2021-07-05 15:38:12 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-07-06 10:36:59 -0700 |
commit | 9a5605505d9c7dbfdb89cc29a8f5fc5cf9fd2334 (patch) | |
tree | 08f03bd63df3506bee57bde496cafb3104078270 /drivers/pps | |
parent | b121693381b112b78c076dea171ee113e237c0e4 (diff) | |
download | linux-9a5605505d9c7dbfdb89cc29a8f5fc5cf9fd2334.tar.gz linux-9a5605505d9c7dbfdb89cc29a8f5fc5cf9fd2334.tar.bz2 linux-9a5605505d9c7dbfdb89cc29a8f5fc5cf9fd2334.zip |
bonding: Add struct bond_ipesc to manage SA
bonding has been supporting ipsec offload.
When SA is added, bonding just passes SA to its own active real interface.
But it doesn't manage SA.
So, when events(add/del real interface, active real interface change, etc)
occur, bonding can't handle that well because It doesn't manage SA.
So some problems(panic, UAF, refcnt leak)occur.
In order to make it stable, it should manage SA.
That's the reason why struct bond_ipsec is added.
When a new SA is added to bonding interface, it is stored in the
bond_ipsec list. And the SA is passed to a current active real interface.
If events occur, it uses bond_ipsec data to handle these events.
bond->ipsec_list is protected by bond->ipsec_lock.
If a current active real interface is changed, the following logic works.
1. delete all SAs from old active real interface
2. Add all SAs to the new active real interface.
3. If a new active real interface doesn't support ipsec offload or SA's
option, it sets real_dev to NULL.
Fixes: 18cb261afd7b ("bonding: support hardware encryption offload to slaves")
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/pps')
0 files changed, 0 insertions, 0 deletions