From: Maxim Uvarov <muvarov@ru.mvista.com>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] drbd-8.0.1 add dependencies to Kconfig
Date: Mon, 26 Mar 2007 14:54:50 +0400 [thread overview]
Message-ID: <4607A67A.7060608@ru.mvista.com> (raw)
In-Reply-To: <200703231440.08564.philipp.reisner@linbit.com>
The errors are:
drivers/block/drbd/drbd_compat_wrappers.h: In function `crypto_hash_digest':
drivers/block/drbd/drbd_compat_wrappers.h:306: warning: implicit
declaration of function `crypto_hmac'
LD .tmp_vmlinux1
drivers/built-in.o: In function `crypto_free_hash':
drivers/block/drbd/drbd_compat_wrappers.h:315: undefined reference to
`crypto_free_tfm'
drivers/block/drbd/drbd_compat_wrappers.h:315: undefined reference to
`crypto_free_tfm'
drivers/built-in.o: In function `drbd_nl_net_conf':
drivers/block/drbd/drbd_compat_wrappers.h:281: undefined reference to
`crypto_alloc_tfm'
drivers/built-in.o: In function `crypto_free_hash':
drivers/block/drbd/drbd_compat_wrappers.h:315: undefined reference to
`crypto_free_tfm'
drivers/block/drbd/drbd_compat_wrappers.h:316: undefined reference to
`crypto_free_tfm'
make: *** [.tmp_vmlinux1] Error 1
I don't know what is behaviour on latest kernels but on 2.6.18
CRYPTO_HMAC is required.
Best regards,
Maxim.
Philipp Reisner wrote:
>Am Mittwoch, 14. März 2007 18:14 schrieb Maxim Uvarov:
>
>
>>Hello all,
>>
>>I have suggestion to add dependencies on CRYPTO and CONNECTOR to the
>>drbr patches
>>to avoid compilation errors due to wrong configuration.
>>What do you think about it? Patches for drbd-8.0.1 are bellow:
>>
>>Best regards,
>>Max Uvarov.
>>
>>
>>--- drbd/Kconfig 2006-11-20 23:05:03.000000000 +0300
>>+++ drbd/Kconfig_new 2007-03-13 19:42:12.000000000 +0300
>>@@ -5,6 +5,9 @@
>> tristate "DRBD Distributed replicated block device support"
>> select INET
>> select PROC_FS
>>+ select CRYPTO
>>+ select CRYPTO_HMAC
>>+ select CONNECTOR
>> ---help---
>> Drbd is a block device which is designed to build high
>>availability
>> clusters. This is done by mirroring a whole block device via (a
>>
>>
>>
>
>
>The "select CONNECTOR" is already there, got in after 8.0.1 was released.
>DRBD should actually compile without the Crypto stuff ( I have not
>verified this in therecent time ). Then the shared secret based
>connection authentification is simply not available.
>
>
>>-ifndef CONFIG_CONNECTOR
>>- drbd-objs += connector.o cn_queue.o
>>-endif
>>-
>>obj-$(CONFIG_BLK_DEV_DRBD) += drbd.o
>>
>>
>
>
>We will keep that part, because it is possible to use DRBD on
>early Linux-2.6.x kernels that did not had the connector in the
>main tree.
>
>-Phil
>
>
prev parent reply other threads:[~2007-03-26 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 17:14 [Drbd-dev] drbd-8.0.1 add dependencies to Kconfig Maxim Uvarov
2007-03-23 13:40 ` Philipp Reisner
2007-03-26 10:54 ` Maxim Uvarov [this message]
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=4607A67A.7060608@ru.mvista.com \
--to=muvarov@ru.mvista.com \
--cc=drbd-dev@lists.linbit.com \
--cc=philipp.reisner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox