Red Hat Bugzilla – Bug 127019
ccsd uses the same protocol family as bluetooth
Last modified: 2010-01-11 21:53:45 EST
Description of problem:
If ccsd is started before the cman module is loaded you get these
messages in the logfile:
Jun 30 18:57:58 link-10 kernel: Bluetooth: Core ver 2.5
Jun 30 18:57:58 link-10 kernel: NET: Registered protocol family 31
Jun 30 18:57:58 link-10 kernel: Bluetooth: HCI device and connection
Jun 30 18:57:58 link-10 kernel: Bluetooth: HCI socket layer initialized
Jun 30 18:57:58 link-10 kernel: Bluetooth: L2CAP ver 2.2
Jun 30 18:57:58 link-10 kernel: Bluetooth: L2CAP socket layer initialized
Jun 30 18:57:58 link-10 kernel: Bluetooth: RFCOMM ver 1.3
Jun 30 18:57:58 link-10 kernel: Bluetooth: RFCOMM socket layer initialized
Jun 30 18:57:58 link-10 kernel: Bluetooth: RFCOMM TTY layer initialized
Both bluetooth and ccsd want to NET: register protocol family 31.
Shouldn't we have something unique?
If you then modprobe the lock_dlm (which pulls in the cman and dlm
modules) it fails with unresolved symbols. ccsd is defined in the
cluster architecture as not being dependent on anything, so it seems
reasonable to start this before loading modules.
[root@link-10 /]# modprobe lock_dlm
WARNING: Error inserting cman
(/lib/modules/2.6.7/kernel/cluster/cman.ko): Operation not permitted
WARNING: Error inserting dlm
(/lib/modules/2.6.7/kernel/cluster/dlm.ko): Unknown symbol in module,
or unknown parameter (see dmesg)
FATAL: Error inserting lock_dlm
Unknown symbol in module, or unknown parameter (see dmesg)
Version-Release number of selected component (if applicable):
[root@link-10 /]# ccsd -V
ccsd DEVEL.1088629082 (built Jun 30 2004 15:59:04)
Copyright (C) Red Hat, Inc. 2004 All rights reserved.
Steps to Reproduce:
3. 'modprobe lock_dlm'
Modules do not load
Modules do load
I don't beleive that the socket family chosen for cman should conflict with
adding patrick to cc list
Changed to 30 as this is unused in the stock 2.6 kernel. It's also the
number TIPC uses and you're unlikely ever to need both at the same
time so this seemed like a good compromise.
Checking in cnxman-socket.h;
new revision: 1.3; previous revision: 1.2
With that change clvmd now cannot connect to cman. The AF_CLUSTER in
lvm needs to match (or refer to same header file for this?).
cnxman-socket.h:#define AF_CLUSTER 31
Err....You must have checked out in a very small window of opportunity...
date: 2004/08/18 16:03:43; author: pcaulfield; state: Exp; lines: +4 -2
Change AF_ number to 30 so it doesn't conflict with bluetooth.
date: 2004/08/18 16:04:35; author: pcaulfield; state: Exp; lines:
Updated file from cman.
Updating version to the right level in the defects. Sorry for the storm.