All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: pull request: bluetooth 2022-07-26:
Date: Tue, 26 Jul 2022 15:13:28 -0700	[thread overview]
Message-ID: <20220726221328.423714-1-luiz.dentz@gmail.com> (raw)

The following changes since commit 9b134b1694ec8926926ba6b7b80884ea829245a0:

  bridge: Do not send empty IFLA_AF_SPEC attribute (2022-07-26 15:35:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2022-07-26

for you to fetch changes up to d0be8347c623e0ac4202a1d4e0373882821f56b0:

  Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put (2022-07-26 13:35:24 -0700)

----------------------------------------------------------------
bluetooth pull request for net:

 - Fix early wakeup after suspend
 - Fix double free on error
 - Fix use-after-free on l2cap_chan_put

----------------------------------------------------------------
Abhishek Pandit-Subedi (1):
      Bluetooth: Always set event mask on suspend

Dan Carpenter (1):
      Bluetooth: mgmt: Fix double free on error path

Luiz Augusto von Dentz (1):
      Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put

 include/net/bluetooth/l2cap.h |  1 +
 net/bluetooth/hci_sync.c      |  6 ++---
 net/bluetooth/l2cap_core.c    | 61 ++++++++++++++++++++++++++++++++++---------
 net/bluetooth/mgmt.c          |  1 -
 4 files changed, 52 insertions(+), 17 deletions(-)

             reply	other threads:[~2022-07-26 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 22:13 Luiz Augusto von Dentz [this message]
2022-07-27  3:00 ` pull request: bluetooth 2022-07-26: patchwork-bot+netdevbpf
2022-08-01 21:15 ` patchwork-bot+bluetooth

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=20220726221328.423714-1-luiz.dentz@gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.