From: mcINEK <mcinek@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [ BUG ] acl sysfs entry remains after connection error
Date: Wed, 8 Oct 2008 17:00:02 +0200 [thread overview]
Message-ID: <e91dafd20810080800o30fe2fb0v7a537715e14c44fa@mail.gmail.com> (raw)
Hi!
I've found a bug in bluetooth stack.
I use bluetooth on ARM Linux machine to simultaneously send pictures
to 2 or 3 devices.
In a L2CAP connection stage (socket L2CAP 'connect') sometimes I get a
'Connection timeout error',
which is not a disaster because I can try to connect again. However
very often I get a kernel error,
which tells me that there is a duplicate entry in sysfs (acl...).
I've checked, and indeed acl connection entries are not removed from
sysfs after a connection fail.
How can I fix this?
PS. I've got latest 2.6.26 kernel.
Regards,
Marcin Undak
next reply other threads:[~2008-10-08 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 15:00 mcINEK [this message]
2008-10-08 15:31 ` [ BUG ] acl sysfs entry remains after connection error Marcel Holtmann
2008-10-15 13:32 ` mcINEK
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=e91dafd20810080800o30fe2fb0v7a537715e14c44fa@mail.gmail.com \
--to=mcinek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox