linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv2 6/6] Bluetooth: Zero bredr pointer when chan is deleted
Date: Mon, 15 Oct 2012 09:50:58 -0300	[thread overview]
Message-ID: <20121015125058.GB6498@joana> (raw)
In-Reply-To: <1350291524-13258-7-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-10-15 11:58:44 +0300]:

> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> 
> If BREDR L2CAP chan is deleted and this chan is the channel through
> which High Speed traffic is routed to AMP then zero pointer to
> the chan in amp_mgr to prevent accessing it.
> 
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
>  net/bluetooth/l2cap_core.c |    4 ++++
>  1 file changed, 4 insertions(+)

All patches but patch 5 were applied to bluetooth-next. Thanks.

	Gustavo

      reply	other threads:[~2012-10-15 12:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 14:09 [RFCv1 1/7] Bluetooth: AMP: Use Loglink handle in ACL Handle field Andrei Emeltchenko
2012-10-12 14:10 ` [RFCv1 2/7] Bluetooth: AMP: Handle complete frames in l2cap Andrei Emeltchenko
2012-10-12 23:50   ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 3/7] Bluetooth: AMP: Drop packets when no l2cap conn exist Andrei Emeltchenko
2012-10-12 23:50   ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 4/7] Bluetooth: Send EFS Conf Rsp only for BR/EDR chan Andrei Emeltchenko
2012-10-12 23:51   ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 5/7] Bluetooth: AMP: Get amp_mgr reference in HS hci_conn Andrei Emeltchenko
2012-10-12 23:53   ` Marcel Holtmann
2012-10-15  8:31     ` Andrei Emeltchenko
2012-10-12 14:10 ` [RFCv1 6/7] Bluetooth: AMP: Zero amp_mgr pointer if removed Andrei Emeltchenko
2012-10-12 23:54   ` Marcel Holtmann
2012-10-12 14:10 ` [RFCv1 7/7] Bluetooth: Zero bredr pointer when chan is deleted Andrei Emeltchenko
2012-10-12 23:54   ` Marcel Holtmann
2012-10-12 23:49 ` [RFCv1 1/7] Bluetooth: AMP: Use Loglink handle in ACL Handle field Marcel Holtmann
2012-10-15  8:58 ` [PATCHv2 0/6] AMP link fixes Andrei Emeltchenko
2012-10-15  8:58   ` [PATCHv2 1/6] Bluetooth: AMP: Use Loglink handle in ACL Handle field Andrei Emeltchenko
2012-10-15  8:58   ` [PATCHv2 2/6] Bluetooth: AMP: Handle complete frames in l2cap Andrei Emeltchenko
2012-10-15  8:58   ` [PATCHv2 3/6] Bluetooth: AMP: Drop packets when no l2cap conn exist Andrei Emeltchenko
2012-10-15  8:58   ` [PATCHv2 4/6] Bluetooth: Send EFS Conf Rsp only for BR/EDR chan Andrei Emeltchenko
2012-10-15  8:58   ` [PATCHv2 5/6] Bluetooth: AMP: Get amp_mgr reference in HS hci_conn Andrei Emeltchenko
2012-10-15 12:49     ` Gustavo Padovan
2012-10-15 13:21       ` Andrei Emeltchenko
2012-10-15 15:27         ` Gustavo Padovan
2012-10-18 10:16           ` [PATCHv2] " Andrei Emeltchenko
2012-10-18 10:28             ` Gustavo Padovan
2012-10-15  8:58   ` [PATCHv2 6/6] Bluetooth: Zero bredr pointer when chan is deleted Andrei Emeltchenko
2012-10-15 12:50     ` Gustavo 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=20121015125058.GB6498@joana \
    --to=gustavo@padovan.org \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@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).