From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Suraj Sumangala <suraj@atheros.com>
Cc: linux-bluetooth@vger.kernel.org, Jothikumar.Mothilal@Atheros.com
Subject: Re: [RFC] Bluetooth: process received S-frames when socket is locked by user process
Date: Wed, 2 Feb 2011 14:28:18 -0200 [thread overview]
Message-ID: <20110202162818.GD2273@joana> (raw)
In-Reply-To: <1296479571-2971-1-git-send-email-suraj@atheros.com>
Hi Suraj,
* Suraj Sumangala <suraj@atheros.com> [2011-01-31 18:42:51 +0530]:
> This patch lets L2CAP process received S-frames even when socket is
> continuously being locked by user process.
>
> This issue was seen when testing with l2test without using "-D" option.
>
> Since the user process does not expect any Rx packets,
> it hogs the socket with continuous call to "send()".
>
> When the TxWindow is full Tx stops untill the I-frames are acked by the receiver.
>
> But the Rx S-Frame acknowleding the Tx frames will stay in the backlog queue
> because the "sock_owned_by_user()" call in l2cap_data_channel()
> will always return true.
>
> The user process does not have an idea about this
> mechanism and keep pumping data and locking the socket and cause a deadlock.
In which kernel are you seeing this error? I think it is already fixed.
Regards,
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-02-02 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 13:12 [RFC] Bluetooth: process received S-frames when socket is locked by user process Suraj Sumangala
2011-02-02 16:28 ` Gustavo F. Padovan [this message]
2011-02-02 16:34 ` Suraj Sumangala
2011-02-02 16:51 ` Gustavo F. Padovan
2011-02-02 17:35 ` Suraj Sumangala
2011-02-02 17:41 ` Gustavo F. Padovan
2011-02-03 6:50 ` Suraj Sumangala
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=20110202162818.GD2273@joana \
--to=padovan@profusion.mobi \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=suraj@atheros.com \
/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).