linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Keith Packard <keithp@keithp.com>,
	linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@intel.com>
Subject: Re: [PATCH] Revert "Bluetooth: Always enable management interface"
Date: Tue, 3 Apr 2012 09:29:46 -0300	[thread overview]
Message-ID: <20120403122946.GA25048@joana> (raw)
In-Reply-To: <20120330065456.GA9173@joana>

Hi Keith,

* Gustavo Padovan <gustavo@padovan.org> [2012-03-30 03:54:56 -0300]:

> Hi Keith,
> 
> * Keith Packard <keithp@keithp.com> [2012-03-28 19:35:44 -0700]:
> 
> > <#part sign=pgpmime>
> > On Wed, 28 Mar 2012 23:28:39 -0300, Gustavo Padovan <gustavo@padovan.org> wrote:
> > 
> > > A consequence is that you'll need to use newer version of bluez, at least 4.99.
> > > Or call the bluetooth daemon (from a pre 4.99 version) with a parameter to
> > > disable the new interface:
> > 
> > That's not OK -- you're breaking user space with this kernel change. I
> > know I get bashed every time I suggest that we 'fix' the kernel and
> > require new user space X bits...
> 
> Can you try the following patch? It should fix the compatibility problem you had.

Did you had chance to test this patch?

	Gustavo

> 
> commit d21c1177b9cf067809ccee2746633cfea3a8b062
> Author: Gustavo Padovan <gustavo@padovan.org>
> Date:   Thu Mar 29 09:47:53 2012 -0300
> 
>     Bluetooth: Fix userspace compatibility issue with mgmt interface
>     
>     To ensure that old user space versions do not accidentally pick up and
>     try to use the management channel, use a different channel number.
>     
>     Reported-by: Keith Packard <keithp@keithp.com>
>     Acked-by: Johan Hedberg <johan.hedberg@intel.com>
>     Acked-by: Marcel Holtmann <marcel@holtmann.org>
>     Signed-off-by: Gustavo Padovan <gustavo@padovan.org>
> 
> diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
> index 344b0f9..ba7f148 100644
> --- a/include/net/bluetooth/hci.h
> +++ b/include/net/bluetooth/hci.h
> @@ -1327,8 +1327,8 @@ struct sockaddr_hci {
>  #define HCI_DEV_NONE   0xffff
>  
>  #define HCI_CHANNEL_RAW                0
> -#define HCI_CHANNEL_CONTROL    1
>  #define HCI_CHANNEL_MONITOR    2
> +#define HCI_CHANNEL_CONTROL    3
>  
>  struct hci_filter {
>         unsigned long type_mask;

  reply	other threads:[~2012-04-03 12:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  1:19 [PATCH] Revert "Bluetooth: Always enable management interface" Keith Packard
2012-03-29  1:25 ` David Miller
2012-03-29  2:25 ` Marcel Holtmann
2012-03-29  2:28 ` Gustavo Padovan
2012-03-29  2:35   ` Keith Packard
2012-03-29  3:33     ` Marcel Holtmann
2012-03-29  4:39       ` David Miller
2012-03-29  4:40     ` David Miller
2012-03-30  6:54     ` Gustavo Padovan
2012-04-03 12:29       ` Gustavo Padovan [this message]
2012-04-05 22:24       ` Keith Packard
2012-04-06  1:01         ` Gustavo Padovan
2012-03-29  3:48   ` Keith Packard
2012-03-29  4:40   ` 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=20120403122946.GA25048@joana \
    --to=gustavo@padovan.org \
    --cc=johan.hedberg@intel.com \
    --cc=keithp@keithp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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).