From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Archie Pusaka <apusaka@google.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
CrosBT Upstreaming <chromeos-bluetooth-upstreaming@chromium.org>,
Archie Pusaka <apusaka@chromium.org>,
Daniel Winkler <danielwinkler@google.com>
Subject: Re: [Bluez PATCH v1] adapter: Don't remove device if adapter is powered off
Date: Mon, 4 Jan 2021 11:09:36 -0800 [thread overview]
Message-ID: <CABBYNZJ8HOLJv6HFCCp1AYMw79nu7rpkQdmLLJR=uvC5CRH03w@mail.gmail.com> (raw)
In-Reply-To: <20201229143408.Bluez.v1.1.I7978a075910600058245dc6891c614cf4c7b004e@changeid>
Hi Archie,
On Mon, Dec 28, 2020 at 10:34 PM Archie Pusaka <apusaka@google.com> wrote:
>
> From: Archie Pusaka <apusaka@chromium.org>
>
> If adapter is powered off when a device is being removed, there is a
> possibility that the kernel couldn't clean the device's information,
> for example the pairing information. This causes the kernel to
> disagree with the user space about whether the device is paired.
>
> Therefore, to avoid discrepancy we must not proceed to remove the
> device within the user space as well.
This sounds like we have a bug in the kernel, aren't we calling
btd_adapter_remove_bonding or is that failing if the adapter is not
powered? Hmm it does like it:
This command can only be used when the controller is powered.
> Reviewed-by: Daniel Winkler <danielwinkler@google.com>
> ---
>
> src/adapter.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/src/adapter.c b/src/adapter.c
> index ec6a6a64c5..a2abc46706 100644
> --- a/src/adapter.c
> +++ b/src/adapter.c
> @@ -1238,6 +1238,14 @@ void btd_adapter_remove_device(struct btd_adapter *adapter,
> {
> GList *l;
>
> + /* Test if adapter is or will be powered off.
> + * This is to prevent removing the device information only on user
> + * space, but failing to do so on the kernel.
> + */
> + if (!(adapter->current_settings & MGMT_SETTING_POWERED) ||
> + (adapter->pending_settings & MGMT_SETTING_POWERED))
> + return;
We might need to return an error here so we can reply with an error on
Adapter.RemoveDevice.
> adapter->connect_list = g_slist_remove(adapter->connect_list, dev);
>
> adapter->devices = g_slist_remove(adapter->devices, dev);
> --
> 2.29.2.729.g45daf8777d-goog
>
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2021-01-04 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 6:34 [Bluez PATCH v1] adapter: Don't remove device if adapter is powered off Archie Pusaka
2020-12-29 6:44 ` [Bluez,v1] " bluez.test.bot
2021-01-04 19:09 ` Luiz Augusto von Dentz [this message]
2021-01-04 19:16 ` [Bluez PATCH v1] " Luiz Augusto von Dentz
2021-01-05 3:17 ` Archie Pusaka
2021-01-05 18:33 ` Luiz Augusto von Dentz
2021-01-06 9:29 ` Archie Pusaka
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='CABBYNZJ8HOLJv6HFCCp1AYMw79nu7rpkQdmLLJR=uvC5CRH03w@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=apusaka@chromium.org \
--cc=apusaka@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=danielwinkler@google.com \
--cc=linux-bluetooth@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).