Revision 1:
  Remove duplicate kfree in dm_register_target.

Revision 2:
  This patch adds a new IV mode, I baptise ''encrypted sector|salt IV'',
  short ESSIV. I describe ESSIV in 
  http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/472
  
  This patch also redefines the syntax of <sector format>. The new syntax
  is:
  
  <cipher>-<chaining mode>-<iv mode>
  
  This has been done to support chaining modes different from CBC mode,
  for example CMC. CMC is not implemented in cryptoapi yet, however I
  would like dm-crypt to be ready for it, so the problems outlined by Adam
  J. Richter in 
  http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/454
  can be fixed easily, by switching to CMC chaining mode. Compatibility
  code has been added to accommodate the old sytnax.
  
  To use ESSIV, set the ivmode (according to the new syntax) to
  "essiv:<hash>". "hash" should be a valid cryptoapi hash. This, for
  example, is a valid dm-target line:
  
  0 200 crypt aes-cbc-essiv:sha256 00000000000000000000000000000000 0 /dev/loop/5 0
  
  Signed-Off-By: Fruhwirth Clemens <clemens@endorphin.org>
  Signed-Off-By: Christophe Saout <christophe@saout.de>

Revision 3:
  DM_TARGET_MSG ioctl

Revision 4:
  Ioctl interface accepts refs by device number, not just name or uuid.

Revision 5:
  Multipath

Revision 6:
  Round-robin path selector.

Revision 7:
  Flakey target

Revision 8:
  kgdb