netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Pull request: bluetooth-2.6 2010-02-05
Date: Fri,  5 Feb 2010 12:05:33 -0800	[thread overview]
Message-ID: <cover.1265399549.git.marcel@holtmann.org> (raw)

Hi Dave,

here are a few more fixes that are mostly a result from the Bluetooth
UnPlugFest testing in Seattle during this week.

The important one are the fix for the sleeping function call in the
RFCOMM timer that show up with certain hardware (not all of them) and
also the fix for double release of the underlaying L2CAP session.

With the HID subsystem changes that turns it into a proper bus, the
HIDP code ended up with a potential case where we access userspace
memory out of the scop of its ioctl() command. Fix this by just keeping
a copy of the HID report descriptor around. The HID subsystem will need
that anyway.

The rest are some SCO/eSCO audio setup fixes with broken hardware and
closing a memory leak in the Marvell driver.

Regards

Marcel


Please pull from

    git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master

This will update the following files:

 drivers/bluetooth/btmrvl_sdio.c |    1 +
 net/bluetooth/hci_conn.c        |    3 ++
 net/bluetooth/hci_event.c       |    1 +
 net/bluetooth/hidp/core.c       |   49 +++++++++++++++++++--------------------
 net/bluetooth/hidp/hidp.h       |    4 ++-
 net/bluetooth/rfcomm/core.c     |    8 ++++-
 6 files changed, 38 insertions(+), 28 deletions(-)

through these ChangeSets:

Marcel Holtmann (1):
    Bluetooth: Fix sleeping function in RFCOMM within invalid context

Michael Poole (1):
    Bluetooth: Keep a copy of each HID device's report descriptor

Nick Pelly (3):
    Bluetooth: Fallback eSCO to SCO on error 0x1a (Unsupported Remote
    Bluetooth: Do not call rfcomm_session_put() for RFCOMM UA on closed
    Bluetooth: Enter active mode before establishing a SCO link.

Yoichi Yuasa (1):
    Bluetooth: Fix memory leak in Marvell BT-over-SDIO driver


             reply	other threads:[~2010-02-05 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 20:05 Marcel Holtmann [this message]
2010-02-05 20:05 ` [PATCH 1/6] Bluetooth: Fallback eSCO to SCO on error 0x1a (Unsupported Remote Feature) Marcel Holtmann
2010-02-05 20:05   ` [PATCH 2/6] Bluetooth: Fix sleeping function in RFCOMM within invalid context Marcel Holtmann
2010-02-05 20:05     ` [PATCH 3/6] Bluetooth: Do not call rfcomm_session_put() for RFCOMM UA on closed socket Marcel Holtmann
2010-02-05 20:05       ` [PATCH 4/6] Bluetooth: Fix memory leak in Marvell BT-over-SDIO driver Marcel Holtmann
2010-02-05 20:05         ` [PATCH 5/6] Bluetooth: Enter active mode before establishing a SCO link Marcel Holtmann
2010-02-05 20:05           ` [PATCH 6/6] Bluetooth: Keep a copy of each HID device's report descriptor Marcel Holtmann
2010-02-09  6:50 ` Pull request: bluetooth-2.6 2010-02-05 David Miller
2010-02-09 15:52   ` Marcel Holtmann
2010-02-09 20:15     ` David Miller

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=cover.1265399549.git.marcel@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --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 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).