All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: clancy_shang@163.com
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	 linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	 zhongjun.yu@quectel.com, Clancy Shang <clancy.shang@quectel.com>
Subject: Re: [PATCH] Bluetooth: mgmt: Fix wrong param be used
Date: Thu, 29 Feb 2024 09:14:22 -0500	[thread overview]
Message-ID: <CABBYNZK1eqfS8Ro8xZXpt-VhfzxxYepkqZamXkipKPGscg6Y8Q@mail.gmail.com> (raw)
In-Reply-To: <20240229084059.895730-1-clancy_shang@163.com>

Hi,

On Thu, Feb 29, 2024 at 3:41 AM <clancy_shang@163.com> wrote:
>
> From: Clancy Shang <clancy.shang@quectel.com>
>
> if the BlueZ library calls the API interface "adapter_set_device_flags",
> which sends the "MGMT_OP_SET_DEVICE_FLAGS" opcode to the kernel, but
> does not receive the callback message "MGMT_EV_DEVICE_FLAGS_CHANGED"
> from the kernel. it fixs this bug.

Please stop sending this change, the client who sent
MGMT_OP_SET_DEVICE_FLAGS is not supposed to get
MGMT_EV_DEVICE_FLAGS_CHANGED back:

https://github.com/bluez/bluez/blob/master/doc/mgmt-api.txt#L4975

If there is a problem with that then perhaps it is in userspace not
setting the flag on command complete.

> Signed-off-by: Clancy Shang <clancy.shang@quectel.com>
> ---
>  net/bluetooth/mgmt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> index 9dd815b6603f..c74abdf3618f 100644
> --- a/net/bluetooth/mgmt.c
> +++ b/net/bluetooth/mgmt.c
> @@ -5177,7 +5177,7 @@ static int set_device_flags(struct sock *sk, struct hci_dev *hdev, void *data,
>
>  done:
>         if (status == MGMT_STATUS_SUCCESS)
> -               device_flags_changed(sk, hdev, &cp->addr.bdaddr, cp->addr.type,
> +               device_flags_changed(NULL, hdev, &cp->addr.bdaddr, cp->addr.type,
>                                      supported_flags, current_flags);
>
>         return mgmt_cmd_complete(sk, hdev->id, MGMT_OP_SET_DEVICE_FLAGS, status,
> --
> 2.25.1
>


-- 
Luiz Augusto von Dentz

  parent reply	other threads:[~2024-02-29 14:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  8:40 [PATCH] Bluetooth: mgmt: Fix wrong param be used clancy_shang
2024-02-29  9:33 ` bluez.test.bot
2024-02-29 14:14 ` Luiz Augusto von Dentz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-25 10:57 [PATCH] " clancy_shang
2024-01-18  7:49 clancy_shang
2024-01-10  7:01 clancy_shang
2024-01-05  9:52 clancy_shang
2024-01-05  3:11 clancy_shang
2024-01-05  8:03 ` Paul Menzel

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=CABBYNZK1eqfS8Ro8xZXpt-VhfzxxYepkqZamXkipKPGscg6Y8Q@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=clancy.shang@quectel.com \
    --cc=clancy_shang@163.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=zhongjun.yu@quectel.com \
    /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.