summaryrefslogtreecommitdiffstats
path: root/sys/netgraph/bluetooth
diff options
context:
space:
mode:
authoremax <emax@FreeBSD.org>2005-04-06 20:54:05 +0000
committeremax <emax@FreeBSD.org>2005-04-06 20:54:05 +0000
commit3ca52382ee57fa71974232af607ce77c438fa8fe (patch)
treef9a17ec9f4b4a85e9619bafd83d3f3a07abefd83 /sys/netgraph/bluetooth
parent6ad4bd8136cdfc2c2e172af511de8f67ba5dba04 (diff)
downloadFreeBSD-src-3ca52382ee57fa71974232af607ce77c438fa8fe.zip
FreeBSD-src-3ca52382ee57fa71974232af607ce77c438fa8fe.tar.gz
Remove PR_ATOMIC flag in ng_btsocket_protosw[] for BLUETOOTH_PROTO_RFCOMM
protocol. RFCOMM is a SOCK_STREAM protocol not SOCK_SEQPACKET. This was a serious bug caused by cut-and-paste. I'm surprised it did not bite me before. Dunce hat goes to me. MFC after: 3 days
Diffstat (limited to 'sys/netgraph/bluetooth')
-rw-r--r--sys/netgraph/bluetooth/socket/ng_btsocket.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/netgraph/bluetooth/socket/ng_btsocket.c b/sys/netgraph/bluetooth/socket/ng_btsocket.c
index 5c977d8..9b8fdd6 100644
--- a/sys/netgraph/bluetooth/socket/ng_btsocket.c
+++ b/sys/netgraph/bluetooth/socket/ng_btsocket.c
@@ -182,7 +182,7 @@ static struct protosw ng_btsocket_protosw[] = {
SOCK_STREAM, /* protocol type */
&ng_btsocket_domain, /* backpointer to domain */
BLUETOOTH_PROTO_RFCOMM, /* protocol */
- PR_ATOMIC | PR_CONNREQUIRED, /* flags */
+ PR_CONNREQUIRED, /* flags */
NULL, NULL, NULL, /* input, output, ctlinput */
ng_btsocket_rfcomm_ctloutput, /* ctloutput */
NULL, /* ousrreq() */
OpenPOWER on IntegriCloud