All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Klug <ski.brimson@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Profile1 close question
Date: Wed, 13 Dec 2017 18:13:09 -0600	[thread overview]
Message-ID: <CADU0Vqxge=ESPPT3YWPt9VCRZCCX=VM5AHBYVnVQsKP3_mveiA@mail.gmail.com> (raw)

The file descriptor that is placed as a parameter to the NewConnection
callback does not close the connection when it is called with the OS's
close.  This is using Bluez 5.47 on Linux.

Bluetoothctl still shows the connection as being up, as does the remote.

What method should one use to close the connection?

I am using Python and GObject Introspection.

Before connection:
rw.py   3983 root    0u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    1u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    2u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    3u     unix 0xceaf54a0      0t0 22976 type=STREAM
rw.py   3983 root    4u  a_inode        0,9        0     7 [eventfd]
rw.py   3983 root    5u  a_inode        0,9        0     7 [eventfd]

After Connection:
NewConnection(/org/bluez/hci0/dev_BC_44_86_56_6B_95, 8)

rw.py   3983 root    0u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    1u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    2u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    3u     unix 0xceaf54a0      0t0 22976 type=STREAM
rw.py   3983 root    4u  a_inode        0,9        0     7 [eventfd]
rw.py   3983 root    5u  a_inode        0,9        0     7 [eventfd]
rw.py   3983 root    8u     sock        0,7      0t0 23050 protocol: RFCOMM

After Close:
rw.py   3983 root    0u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    1u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    2u      CHR      136,3      0t0     6 /dev/pts/3
rw.py   3983 root    3u     unix 0xceaf54a0      0t0 22976 type=STREAM
rw.py   3983 root    4u  a_inode        0,9        0     7 [eventfd]
rw.py   3983 root    5u  a_inode        0,9        0     7 [eventfd]


Device BC:44:86:56:6B:95
...
Connected: yes

             reply	other threads:[~2017-12-14  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  0:13 John Klug [this message]
2017-12-14 15:21 ` Profile1 close question John Klug
2017-12-14 15:35   ` Szymon Janc
2017-12-14 16:08     ` Luiz Augusto von Dentz

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='CADU0Vqxge=ESPPT3YWPt9VCRZCCX=VM5AHBYVnVQsKP3_mveiA@mail.gmail.com' \
    --to=ski.brimson@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.