diff options
| author | Joy Latten <latten@austin.ibm.com> | 2007-08-02 19:25:43 -0700 |
|---|---|---|
| committer | David S. Miller <davem@sunset.davemloft.net> | 2007-08-02 19:42:29 -0700 |
| commit | 4a4b6271a8df417e328aed4c8a7e04e0b282207e (patch) | |
| tree | a1080744f58a4aa0864453f989966b2df64df41c /crypto | |
| parent | 3516ffb0fef710749daf288c0fe146503e0cf9d4 (diff) | |
| download | linux-stable-4a4b6271a8df417e328aed4c8a7e04e0b282207e.tar.gz linux-stable-4a4b6271a8df417e328aed4c8a7e04e0b282207e.tar.bz2 linux-stable-4a4b6271a8df417e328aed4c8a7e04e0b282207e.zip | |
[PF_KEY]: Fix ipsec not working in 2.6.23-rc1-git10
Although an ipsec SA was established, kernel couldn't seem to find it.
I think since we are now using "x->sel.family" instead of "family" in
the xfrm_selector_match() called in xfrm_state_find(), af_key needs to
set this field too, just as xfrm_user.
In af_key.c, x->sel.family only gets set when there's an
ext_hdrs[SADB_EXT_ADDRESS_PROXY-1] which I think is for tunnel.
I think pfkey needs to also set the x->sel.family field when it is 0.
Tested with below patch, and ipsec worked when using pfkey.
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions