From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Mika Linnanoja <mika.linnanoja@nokia.com>
Cc: linux-bluetooth@vger.kernel.org,
ext Ville Tervo <ville.tervo@nokia.com>,
Antti Julku <antti.julku@nokia.com>,
ext Marcel Holtmann <marcel@holtmann.org>,
Lukasz Rymanowski <lukasz.rymanowski@tieto.com>,
linus.walleij@stericsson.com,
par-gunnar.p.hjalmdahl@stericsson.com
Subject: Re: [PATCH] bluetooth: Fix for security block issue.
Date: Thu, 5 May 2011 16:02:30 -0300 [thread overview]
Message-ID: <20110505190230.GC2098@joana> (raw)
In-Reply-To: <4DBA6D97.7050207@nokia.com>
Hi Mika,
* Mika Linnanoja <mika.linnanoja@nokia.com> [2011-04-29 10:49:43 +0300]:
> On 04/28/2011 12:51 PM, ext Ville Tervo wrote:
> > Could the actual reason be some change in usb stack? Could it have lower
> > priority for event pipe than for data pipe? In that case event for security
> > change might arrive to bt stack too late.
> >
> > At lest I haven't seen this kind of behaviour with serial attached chips. So I
> > think this is something USB specific.
>
> Happens on Ubuntu 11.04 (released yesterday; bluez 4.91 & kernel 2.6.38-8) as
> well, tested with White PTS 2.1 dongle (CSR chip) on laptop x61s. Sending
> party (OPP with obex-client in a loop) was a phone.
Is this an regression? Or did it never happen before?
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-05-05 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 14:27 [PATCH] bluetooth: Fix for security block issue Lukasz Rymanowski
2011-01-25 16:13 ` Marcel Holtmann
2011-04-28 9:39 ` Antti Julku
2011-04-28 9:51 ` Ville Tervo
2011-04-29 7:49 ` Mika Linnanoja
2011-05-04 7:53 ` Lukasz.Rymanowski
2011-05-04 15:03 ` Luiz Augusto von Dentz
2011-05-05 19:09 ` Gustavo F. Padovan
2011-09-21 7:22 ` Antti Julku
2011-09-21 8:01 ` Marcel Holtmann
2011-05-05 19:02 ` Gustavo F. Padovan [this message]
2011-05-06 6:10 ` Mika Linnanoja
2011-05-06 7:28 ` Mika Linnanoja
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=20110505190230.GC2098@joana \
--to=padovan@profusion.mobi \
--cc=antti.julku@nokia.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lukasz.rymanowski@tieto.com \
--cc=marcel@holtmann.org \
--cc=mika.linnanoja@nokia.com \
--cc=par-gunnar.p.hjalmdahl@stericsson.com \
--cc=ville.tervo@nokia.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).