[PATCH 0/5] Partial (de)compression Crypto API

[Geert Uytterhoeven]

The following patch series adds support for partial (de)compression to the
CRYPTO API, and modifies SquashFS 4 to use this:

  [1] crypto: compress - Add pcomp interface
  [2] crypto: testmgr - Add support for the pcomp interface
  [3] crypto: new zlib crypto module, using pcomp
  [4] crypto: testmgr - add zlib test
  [5] squashfs: Make SquashFS 4 use the new pcomp crypto interface

The patches are based on:
  linux-2.6.git + cryptodev-2.6.git + commit 3f683d61 ("crypto: api - Fix
  crypto_alloc_tfm/create_create_tfm return convention")

Changes since last version (2009-02-13):
  - Convert crypto_pcomp to a new-style crypto module, using crypto_alloc_tfm()
    instead of crypto_alloc_base()
  - Pass crypto_pcomp pointers instead of crypto_tfm pointers where appropriate
  - Use crypto_destroy_tfm() instead of crypto_free_tfm(), to take into account
    the offset info the slab object
  - Remove redundant check for CRYPTO_ALG_TYPE_PCOMPRESS in
    crypto_pcomp_init_tfm()
  - Use separate setup functions for compression and decompression
  - Sanitize naming to crypto_{,de}compress_{setup,init,update,final}()
  - Remove backwards-compatibility layer (export pcomp through comp), as
    requested by Herbert Xu
  - Create a new "zlib" pcomp module instead of modifying the existing
    "deflate" comp module 
  - Readd accidentally removed ".cra_module = THIS_MODULE", which allowed the
    zlib module to be rmmoded while it was in use
  - Fix the pcomp/testmgr dependency

With kind regards,

Geert Uytterhoeven
Software Architect

Sony Techsoft Centre Europe
The Corporate Village  Da Vincilaan 7-D1  B-1935 Zaventem  Belgium

Phone:    +32 (0)2 700 8453
Fax:      +32 (0)2 700 8622
E-mail:   Geert.Uytterhoeven@xxxxxxxxxxx
Internet: http://www.sony-europe.com/

A division of Sony Europe (Belgium) N.V.
VAT BE 0413.825.160 Â RPR Brussels
Fortis  BIC GEBABEBB  IBAN BE41293037680010
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/