[IPSEC]: Store xfrm states in security path directly

Browse source

As it is xfrm_input first collects a list of xfrm states on the stack
before storing them in the packet's security path just before it
returns.  For async crypto, this construction presents an obstacle
since we may need to leave the loop after each transform.

In fact, it's much easier to just skip the stack completely and always
store to the security path.  This is proven by the fact that this
patch actually shrinks the code.

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Herbert Xu 2007-11-13 21:44:55 -08:00 • committed by David S. Miller

parent 716062fd4c

commit b2aa5e9d43

1 changed files with 15 additions and 27 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

42

net/xfrm/xfrm_input.c

View file