Hi,

A few minor issues.

1.  CONFIG_CRYPTO_HMAC can be defined as a module; the drbd code 
currently requires it to be built into the kernel, apparently for no 
good reason.

2.  If the hash algorithm itself isn't available (like sha1.ko wasn't 
loaded yet), crypto_alloc_hash() returns -ENOENT.  It does not return 
NULL, which is what the drbd code currently checks for.  This leads to 
crashes later.

3.  Once #2 is fixed, the user tools try to report the error, and the 
error message contains a typo, an extra ")".  "Failure: (120) The 
'cram-hmac-alg' you specified is not known in )the kernel."  It also 
doesn't tell the user what to do to fix it.

The attached patch fixes the above issues, and applies cleanly to your 
current svn.  Please review and apply.

Mark

P.S.  Since drbd no longer requires any exported symbols from the 
hmac/hash module, is there any reason to check CONFIG_CRYPTO_HMAC at 
all?  A simpler check on CONFIG_CRYPTO to make sure the basic API exists 
should be all you need...