On Wed, Aug 01, 2007 at 07:02:14PM -0400, Maurice Volaski wrote:
First, did you confirm this behavior? Can you please explain that? How
could they possibly interact with one another?
It's obvious when looking at the source code that both modules you are
trying to use are buggy, and the sum of the bugs in both modules is the
drbd breakage you observe.
30% of the guilt go to the drbd developers for doing the following:
#ifdef NETLINK_ROUTE6
/* pre 2.6.16 */
err = cn_init();
if(err) return err;
#endif
The author wanted to check for pre-2.6.14 when the connector code was
added to the kernel, not for pre-2.6.16 as the comment implies or
pre-2.6.13 as the code does.
Or he wanted to check whether it's a recent kernel and the connector
code is compiled into the kernel.
70% of the guilt go to the web100 developers for shipping the following
to their users:
--- linux-2.6-web100/include/linux/netlink.h 19 Jul 2007 17:49:17
-0000 1.1.1.16
+++ linux-2.6-web100/include/linux/netlink.h 19 Jul 2007 18:11:01
-0000 1.17
@@ -14,6 +14,7 @@
#define NETLINK_SELINUX 7 /* SELinux event
notifications */
#define NETLINK_ISCSI 8 /* Open-iSCSI */
#define NETLINK_AUDIT 9 /* auditing */
+#define NETLINK_ROUTE6 11 /* af_inet6 route
comm channel */
#define NETLINK_FIB_LOOKUP 10
#define NETLINK_CONNECTOR 11
#define NETLINK_NETFILTER 12 /* netfilter subsystem */
That's not only buggy but also not used by web100.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed