Revision 1:
  Remove duplicate kfree in dm_register_target error path.
  
  Signed-Off-By: Alasdair G Kergon <agk@redhat.com>

Revision 2:
  Use %llu not %Lu in sscanf/printf format strings.
  
  Signed-Off-By: Alasdair G Kergon <agk@redhat.com>

Revision 3:
  Small tidy-ups:
  - Use unsigned consistently
  - Simplify crypt_iv_plain memset
  - Use DMEMIT macro
   
  Signed-Off-By: Alasdair G Kergon <agk@redhat.com>
  Signed-Off-By: Christophe Saout <christophe@saout.de>

Revision 4:
  Create crypt_iv_operations structure with generator method
  and move the plain iv generator into this structure.
   
  Optionally accept an extended <sector format> syntax:
    <cipher>-<chaining mode>-<iv mode>
  
  This also makes it ready to support chaining modes other than CBC 
  mode, such as CMC (not implemented in cryptoapi yet), 
  The problems outlined by Adam J. Richter in
    http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/454
  would be fixed by switching to CMC chaining mode. 
  
  Example of a valid target line:
    0 200 crypt aes-cbc-plain 00000000000000000000000000000000 0 /dev/loop/5 0
   
  Signed-Off-By: Alasdair G Kergon <agk@redhat.com>
  Signed-Off-By: Christophe Saout <christophe@saout.de>

Revision 5:
  This patch adds a new IV mode, I baptise ''encrypted sector|salt IV''
  I describe ESSIV in
    http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/472
  
  To use ESSIV, set the ivmode (using 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: Alasdair G Kergon <agk@redhat.com>
  Signed-Off-By: Christophe Saout <christophe@saout.de>
  Signed-Off-By: Fruhwirth Clemens <clemens@endorphin.org>

Revision 6:
  DM_TARGET_MSG ioctl to send a message to a dm target instance

Revision 7:
  Ioctl interface accepts refs by device number, not just name or uuid.
  
  Signed-Off-By: Alasdair G Kergon <agk@redhat.com>

Revision 8:
  Multipath

Revision 9:
  Fix missing error path up_read(&_ps_lock).

Revision 10:
  Remove stray semicolon.
  
  I've found the most severe bug report ever! ;-)
  
  You got a stray semicolon in dm.c, around :809
  +       atomic_inc(&md->event_nr);;
  
  Signed-Off-By: Alasdair G Kergon <agk@redhat.com>
  From: Lars Marowsky-Bree <lmb@suse.de>

Revision 11:
  Round-robin path selector.

Revision 12:
  Flakey target

Revision 13:
  kgdb