From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Vladislav P <vladisslav@inbox.ru>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: rfcomm: Release BTM while sleeping to avoid deadlock.
Date: Mon, 14 Feb 2011 15:25:16 -0200 [thread overview]
Message-ID: <20110214172516.GF2597@joana> (raw)
In-Reply-To: <E1Pp0gh-0002s9-00.vladisslav-inbox-ru@f95.mail.ru>
Hi Vladislav,
* Vladislav P <vladisslav@inbox.ru> [2011-02-14 18:50:07 +0300]:
> Mon, 14 Feb 2011 12:49:31 -0200 письмо от "Gustavo F. Padovan" <padovan@profusion.mobi>:
>
> > Hi
> >
> > * Владислав <vladisslav@inbox.ru> [2011-02-13 04:01:45 +0300]:
> >
> > > Bug description:
> > > Kernel freezes for ~2 seconds after trying to access /dev/rfcommX device.
> > > Steps to reproduce:
> > > 1. Edit /etc/bluetooth/rfcomm.conf - uncomment default config, set "bind" to
> > "yes".
> > > 2. Issue "sudo rfcomm bind all" to create /dev/rfcomm0 device node.
> > > 3. Issue "cat /dev/rfcomm0" to trigger a bug.
> > > Everything freezes (at least GUI): cursor does not move, no response from
> > > keypresses, no gui redraw for 2~3 seconds.
> > > Then cat displays expected error message "cat: /dev/rfcomm0: Host is down"
> > > and system starts to respond again.
> > > What expected (and occurs with 2.6.35) : no freeze between cat and error
> > message.
> > > Things goes worse when device, mentioned in /etc/bluetooth/rfcomm.conf
> > > is in range and not paired - system displays pairing request and locks
> > > up for a longer time, maybe completely - I did not wait longer than ~30
> > > seconds and turned off bluetooth device.
> >
> > I've faced this issue some days ago and your patch looks good. But I need
> > proper git patch with your Signed-off-by line.
> >
> > --
> > Gustavo F. Padovan
> > http://profusion.mobi
> Made proper patch:
>
> From d1459f3042b4b8cdea1f1a184eb61f7be4002203 Mon Sep 17 00:00:00 2001
> From: Vladislav P <vladisslav@inbox.ru>
> Date: Mon, 14 Feb 2011 18:42:27 +0300
> Subject: [PATCH] Release BTM while sleeping to avoid deadlock.
>
> Signed-off-by: Vladislav P <vladisslav@inbox.ru>
> ---
> net/bluetooth/rfcomm/tty.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
Applied, thanks.
--
Gustavo F. Padovan
http://profusion.mobi
prev parent reply other threads:[~2011-02-14 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 1:01 [PATCH] Bluetooth: rfcomm: Release BTM while sleeping to avoid deadlock Владислав
2011-02-14 14:49 ` Gustavo F. Padovan
[not found] ` <E1Pp0gh-0002s9-00.vladisslav-inbox-ru@f95.mail.ru>
2011-02-14 17:25 ` Gustavo F. Padovan [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=20110214172516.GF2597@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vladisslav@inbox.ru \
/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).