RFC IPsec: convert to ahash
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest7 patches 11 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | esp: Add an additional scatterlist entry for the assoc datanet/ net/ | +36 | 0 replies | |
| 2/7 | crypto: authenc - convert to ahashcrypto/ | +150 | 7 replies | |
| 3/7 | ah: Add struct crypto_ahash to ah_datainclude/ | +1 | 0 replies | |
| 4/7 | ah4: convert to ahashnet/ | +236 | 1 reply | |
| 5/7 | ah6: convert to ahashnet/ | +272 | 0 replies | |
| 6/7 | ah: Remove obsolete codeinclude/ | +3 | 0 replies | |
| 7/7 | xfrm: remove skb_icv_walkinclude/ net/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC] [PATCH 0/7] IPsec: convert to ahash
This patchset converts IPsec over to the new ahash interface. The pachset applies to cryptodev-2.6. I was able to test the synchronous codepaths, the asynchronous ones are untested.
I'm still somewhat unhappy with the ahash version of authenc, but I decided to post anyway as a base for discussion.
Since the calls to the hash algorithms can now return asynchronous, I'd like to avoid multiple calls to the hash update functions. I'd rather like to do all the hashing with one call to crypto_ahash_digest(). As it is, this requires chaining of all the involved scatterlists. Since we still can't use sg_chain() to chain up the lists, I added an additional scatterlist entry to the scatterlist of the assoc data (esp) to be able to chain later in the crypto layer. To keep compatibility I set the termination bit at the first entry and remove it later in authenc. In fact to rely on this additional entry and just to remove the termintation bit later makes me a bit nervous and I'm not sure whether this is acceptable, so better ideas are very welcome.
Steffen