Re: xfrm_input() and ->seq oddities

On Sun, Feb 03, 2008 at 12:37:19AM +0000, Al Viro wrote:

This is still very odd...  Where do you initialize ->seq.input?  What

In xfrm_input.

guarantees that async call of xfrm_input() will be always preceded by
at least one non-async one?

OK I admit it isn't pretty.  But the encap_type argument is reused to
indicate async resumption.  That is, if we enter with encap_type < 0,
it means that we're resuming a previous operation and seq.input has
therefore been set by the previous xfrm_input call.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt