linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org, linus.walleij@stericsson.com,
	par-gunnar.p.hjalmdahl@stericsson.com, padovan@profusion.mobi
Subject: Re: [PATCH] bluetooth: Fix for security block issue.
Date: Tue, 25 Jan 2011 17:13:10 +0100	[thread overview]
Message-ID: <1295971990.1520.53.camel@aeonflux> (raw)
In-Reply-To: <1295965639-16683-1-git-send-email-lukasz.rymanowski@tieto.com>

Hi Lukasz,

> It can happen that controller will schedule ACL data
> containing L2CAP connect request to host just before
> encryption change event, even though link is encrypted on
> LMP level before L2CAP connect request come.
> With this fix, L2CAP layer will handle such scenario.

I really don't like to have a work around for this. It is clearly a bug
in the controller.

Regards

Marcel



  reply	other threads:[~2011-01-25 16:13 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 [this message]
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
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=1295971990.1520.53.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.com \
    --cc=padovan@profusion.mobi \
    --cc=par-gunnar.p.hjalmdahl@stericsson.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).