Hi John,
A few fixes for 3.13. There is 3 fixes to the RFCOMM protocol. One crash fix to
L2CAP. A simple fix to a bad behaviour in the SMP protocol, and last, an
revert, that I sent in the last pull request but doesn't seem to be in your
tree.
Please pull or let me know of any issues. Thanks!
Gustavo
---
The following changes since commit 8ce9beac4661f576ea0d518b9f086bb52a171a37:
drivers: net: wireless: b43: Fix possible NULL ptr dereference (2013-10-18 13:41:11 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth master
for you to fetch changes up to 3244d4a55c95708b0fa6fd820a9009534ed08a5f:
Bluetooth: Fix rejecting SMP security request in slave role (2013-11-11 15:48:36 -0200)
----------------------------------------------------------------
Hans de Goede (1):
Bluetooth: revert: "Bluetooth: Add missing reset_resume dev_pm_ops"
Johan Hedberg (1):
Bluetooth: Fix rejecting SMP security request in slave role
Marcel Holtmann (1):
Bluetooth: Fix issue with RFCOMM getsockopt operation
Seung-Woo Kim (3):
Bluetooth: Fix RFCOMM bind fail for L2CAP sock
Bluetooth: Fix to set proper bdaddr_type for RFCOMM connect
Bluetooth: Fix crash in l2cap_chan_send after l2cap_chan_del
drivers/bluetooth/btusb.c | 1 -
net/bluetooth/l2cap_core.c | 3 +++
net/bluetooth/rfcomm/core.c | 3 +++
net/bluetooth/rfcomm/sock.c | 6 +++++-
net/bluetooth/smp.c | 3 +++
5 files changed, 14 insertions(+), 2 deletions(-)
On Fri, Nov 15, 2013 at 01:15:54PM -0200, Gustavo Padovan wrote:
> Hi John,
>
> 2013-11-11 John W. Linville <[email protected]>:
>
> > On Mon, Nov 11, 2013 at 04:27:38PM -0200, Gustavo Padovan wrote:
> > > Hi John,
> > >
> > > A few fixes for 3.13. There is 3 fixes to the RFCOMM protocol. One crash fix to
> > > L2CAP. A simple fix to a bad behaviour in the SMP protocol, and last, an
> > > revert, that I sent in the last pull request but doesn't seem to be in your
> > > tree.
> >
> > Are you looking in the wireless-next tree? It seems to be there, no?
>
> Yes, it is there. I'm resending this pull request without it:
>
> Please pull or let me know of any problems! Thanks
>
> Gustavo
>
> ---
>
> The following changes since commit 8ce9beac4661f576ea0d518b9f086bb52a171a37:
>
> drivers: net: wireless: b43: Fix possible NULL ptr dereference (2013-10-18 13:41:11 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth for-upstream
>
> for you to fetch changes up to 86ca9eac31d0d8c4fe61b5726e6d63197bc435a6:
>
> Bluetooth: Fix rejecting SMP security request in slave role (2013-11-13 11:36:54 -0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
Hi John,
2013-11-11 John W. Linville <[email protected]>:
> On Mon, Nov 11, 2013 at 04:27:38PM -0200, Gustavo Padovan wrote:
> > Hi John,
> >
> > A few fixes for 3.13. There is 3 fixes to the RFCOMM protocol. One crash fix to
> > L2CAP. A simple fix to a bad behaviour in the SMP protocol, and last, an
> > revert, that I sent in the last pull request but doesn't seem to be in your
> > tree.
>
> Are you looking in the wireless-next tree? It seems to be there, no?
Yes, it is there. I'm resending this pull request without it:
Please pull or let me know of any problems! Thanks
Gustavo
---
The following changes since commit 8ce9beac4661f576ea0d518b9f086bb52a171a37:
drivers: net: wireless: b43: Fix possible NULL ptr dereference (2013-10-18 13:41:11 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth for-upstream
for you to fetch changes up to 86ca9eac31d0d8c4fe61b5726e6d63197bc435a6:
Bluetooth: Fix rejecting SMP security request in slave role (2013-11-13 11:36:54 -0200)
----------------------------------------------------------------
Johan Hedberg (1):
Bluetooth: Fix rejecting SMP security request in slave role
Marcel Holtmann (1):
Bluetooth: Fix issue with RFCOMM getsockopt operation
Seung-Woo Kim (3):
Bluetooth: Fix RFCOMM bind fail for L2CAP sock
Bluetooth: Fix to set proper bdaddr_type for RFCOMM connect
Bluetooth: Fix crash in l2cap_chan_send after l2cap_chan_del
net/bluetooth/l2cap_core.c | 3 +++
net/bluetooth/rfcomm/core.c | 3 +++
net/bluetooth/rfcomm/sock.c | 6 +++++-
net/bluetooth/smp.c | 3 +++
4 files changed, 14 insertions(+), 1 deletion(-)
Hi Gustavo,
> A few fixes for 3.13. There is 3 fixes to the RFCOMM protocol. One crash fix to
> L2CAP. A simple fix to a bad behaviour in the SMP protocol, and last, an
> revert, that I sent in the last pull request but doesn't seem to be in your
> tree.
>
> Please pull or let me know of any issues. Thanks!
>
>
> Gustavo
>
> ---
> The following changes since commit 8ce9beac4661f576ea0d518b9f086bb52a171a37:
>
> drivers: net: wireless: b43: Fix possible NULL ptr dereference (2013-10-18 13:41:11 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth master
>
> for you to fetch changes up to 3244d4a55c95708b0fa6fd820a9009534ed08a5f:
>
> Bluetooth: Fix rejecting SMP security request in slave role (2013-11-11 15:48:36 -0200)
>
> ----------------------------------------------------------------
> Hans de Goede (1):
> Bluetooth: revert: "Bluetooth: Add missing reset_resume dev_pm_ops?
this one is already in net-next actually. John pushed bluetooth and bluetooth-next to Dave at the same time.
> Johan Hedberg (1):
> Bluetooth: Fix rejecting SMP security request in slave role
>
> Marcel Holtmann (1):
> Bluetooth: Fix issue with RFCOMM getsockopt operation
>
> Seung-Woo Kim (3):
> Bluetooth: Fix RFCOMM bind fail for L2CAP sock
> Bluetooth: Fix to set proper bdaddr_type for RFCOMM connect
> Bluetooth: Fix crash in l2cap_chan_send after l2cap_chan_del
These 5 fixes are still needed.
Regards
Marcel
On Mon, Nov 11, 2013 at 04:27:38PM -0200, Gustavo Padovan wrote:
> Hi John,
>
> A few fixes for 3.13. There is 3 fixes to the RFCOMM protocol. One crash fix to
> L2CAP. A simple fix to a bad behaviour in the SMP protocol, and last, an
> revert, that I sent in the last pull request but doesn't seem to be in your
> tree.
Are you looking in the wireless-next tree? It seems to be there, no?
John
>
> Please pull or let me know of any issues. Thanks!
>
>
> Gustavo
>
> ---
> The following changes since commit 8ce9beac4661f576ea0d518b9f086bb52a171a37:
>
> drivers: net: wireless: b43: Fix possible NULL ptr dereference (2013-10-18 13:41:11 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth master
>
> for you to fetch changes up to 3244d4a55c95708b0fa6fd820a9009534ed08a5f:
>
> Bluetooth: Fix rejecting SMP security request in slave role (2013-11-11 15:48:36 -0200)
>
> ----------------------------------------------------------------
> Hans de Goede (1):
> Bluetooth: revert: "Bluetooth: Add missing reset_resume dev_pm_ops"
>
> Johan Hedberg (1):
> Bluetooth: Fix rejecting SMP security request in slave role
>
> Marcel Holtmann (1):
> Bluetooth: Fix issue with RFCOMM getsockopt operation
>
> Seung-Woo Kim (3):
> Bluetooth: Fix RFCOMM bind fail for L2CAP sock
> Bluetooth: Fix to set proper bdaddr_type for RFCOMM connect
> Bluetooth: Fix crash in l2cap_chan_send after l2cap_chan_del
>
> drivers/bluetooth/btusb.c | 1 -
> net/bluetooth/l2cap_core.c | 3 +++
> net/bluetooth/rfcomm/core.c | 3 +++
> net/bluetooth/rfcomm/sock.c | 6 +++++-
> net/bluetooth/smp.c | 3 +++
> 5 files changed, 14 insertions(+), 2 deletions(-)
>
--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.