All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Glines <mark@glines.org>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] drbd-svn can't handle modular hmac, and crashes if hash can't be found
Date: Sun, 14 Jan 2007 09:18:44 -0800	[thread overview]
Message-ID: <45AA65F4.90709@glines.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

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...

[-- Attachment #2: drbd-hmac-fixes.diff --]
[-- Type: text/plain, Size: 1728 bytes --]

Index: drbd/drbd_receiver.c
===================================================================
--- drbd/drbd_receiver.c	(revision 2687)
+++ drbd/drbd_receiver.c	(working copy)
@@ -2894,7 +2894,7 @@
 	return 0;
 }
 
-#ifndef CONFIG_CRYPTO_HMAC
+#if !defined(CONFIG_CRYPTO_HMAC) && !defined(CONFIG_CRYPTO_HMAC_MODULE)
 STATIC int drbd_do_auth(drbd_dev *mdev)
 {
 	ERR( "This kernel was build without CONFIG_CRYPTO_HMAC.\n");
Index: drbd/drbd_nl.c
===================================================================
--- drbd/drbd_nl.c	(revision 2687)
+++ drbd/drbd_nl.c	(working copy)
@@ -1052,7 +1052,8 @@
 	if( new_conf->cram_hmac_alg[0] != 0) {
 		snprintf(hmac_name,HMAC_NAME_L,"hmac(%s)",new_conf->cram_hmac_alg);
 		tfm = crypto_alloc_hash(hmac_name, 0, CRYPTO_ALG_ASYNC);
-		if (tfm == NULL) {
+		if (IS_ERR(tfm)) {
+			tfm = NULL;
 			retcode=CRAMAlgNotAvail;
 			goto fail;
 		}
Index: user/drbdsetup.c
===================================================================
--- user/drbdsetup.c	(revision 2687)
+++ user/drbdsetup.c	(working copy)
@@ -359,8 +359,8 @@
 	EM(MDIOError) = "IO error(s) orruced during initial access to meta-data.\n",
 	EM(MDInvalid) = "No valid meta-data signature found.\n)"
 	"Use 'drbdadm create-md res' to initialize meta-data area.\n",
-	EM(CRAMAlgNotAvail) = "The 'cram-hmac-alg' you specified is not known in )"
-	"the kernel.\n",
+	EM(CRAMAlgNotAvail) = "The 'cram-hmac-alg' you specified is not known in "
+	"the kernel. (maybe you need to modprobe it, or modprobe hmac?)\n",
 	EM(CRAMAlgNotDigest) = "The 'cram-hmac-alg' you specified is not a digest.",
 	EM(KMallocFailed) = "kmalloc() failed. Out of memory?",
 	EM(DiscardNotAllowed) = "--discard-my-data not allowed when primary.",

             reply	other threads:[~2007-01-15  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 17:18 Mark Glines [this message]
2007-01-15  7:45 ` [Drbd-dev] drbd-svn can't handle modular hmac, and crashes if hash can't be found Lars Ellenberg
2007-01-15  7:52   ` Mark Glines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45AA65F4.90709@glines.org \
    --to=mark@glines.org \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.