From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: netdev@vger.kernel.org
Subject: Re: [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue
Date: Sun, 17 Sep 2006 21:32:10 +0300 [thread overview]
Message-ID: <20060917183210.GA24913@ee.oulu.fi> (raw)
In-Reply-To: <1158495506.6665.0.camel@localhost>
On Sun, Sep 17, 2006 at 02:18:26PM +0200, Marcel Holtmann wrote:
> Hi Pekka,
>
> > Got this from a 2.6.18rc7-based fedora-devel kernel:
> >
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > 2.6.17-1.2647.fc6 #1
> > sdpd/4955 is trying to acquire lock:
> > (sk_lock-AF_BLUETOOTH){--..}, at: [<f0cea241>] bt_accept_dequeue+0x26/0xc6 [bluetooth]
>
> what where you doing when this happened?
Hiya
Hmn. Plugged my USB BT dongle in, started gnome-obex-server and sent a few
pictures from my cellphone to the box, nothing fancy.. Bluetooth daemons
running obviously at this time...
prev parent reply other threads:[~2006-09-17 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 11:36 [Bluetooth] recursive locking in l2cap_sock_accept/bt_accept_dequeue Pekka Pietikainen
2006-09-17 12:18 ` Marcel Holtmann
2006-09-17 18:32 ` Pekka Pietikainen [this message]
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=20060917183210.GA24913@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=marcel@holtmann.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).