From: "Gix, Brian" <brian.gix@intel.com>
To: "mat.jonczyk@o2.pl" <mat.jonczyk@o2.pl>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
"marcel@holtmann.org" <marcel@holtmann.org>
Subject: Re: [PATCH] Bluetooth: silence a dmesg error message in hci_request.c
Date: Thu, 17 Nov 2022 20:34:16 +0000 [thread overview]
Message-ID: <499a1278bcf1b2028f6984d61733717a849d9787.camel@intel.com> (raw)
In-Reply-To: <20221116202856.55847-1-mat.jonczyk@o2.pl>
Hi Mateusz,
On Wed, 2022-11-16 at 21:28 +0100, Mateusz Jończyk wrote:
> On kernel 6.1-rcX, I have been getting the following dmesg error
> message
> on every boot, resume from suspend and rfkill unblock of the
> Bluetooth
> device:
>
> Bluetooth: hci0: HCI_REQ-0xfcf0
>
This has a patch that fixes the usage of the deprecated HCI_REQ
mechanism rather than hiding the fact it is being called, as in this
case.
I am still waiting for someone to give me a "Tested-By:" tag to patch:
[PATCH 1/1] Bluetooth: Convert MSFT filter HCI cmd to hci_sync
Which will also stop the dmesg error. If you could try that patch, and
resend it to the list with a Tested-By tag, it can be applied.
We still want to be allerted to deprecated usage situations.
> After some investigation, it turned out to be caused by
> commit dd50a864ffae ("Bluetooth: Delete unreferenced hci_request
> code")
> which modified hci_req_add() in net/bluetooth/hci_request.c to always
> print an error message when it is executed. In my case, the function
> was
> executed by msft_set_filter_enable() in net/bluetooth/msft.c, which
> provides support for Microsoft vendor opcodes.
>
> As explained by Brian Gix, "the error gets logged because it is using
> a
> deprecated (but still working) mechanism to issue HCI opcodes" [1].
> So
> this is just a debugging tool to show that a deprecated function is
> executed. As such, it should not be included in the mainline kernel.
> See for example
> commit 771c035372a0 ("deprecate the '__deprecated' attribute warnings
> entirely and for good")
> Additionally, this error message is cryptic and the user is not able
> to
> do anything about it.
>
> [1]
> Link:
> https://lore.kernel.org/lkml/beb8dcdc3aee4c5c833aa382f35995f17e7961a1.camel@intel.com/
>
> Fixes: dd50a864ffae ("Bluetooth: Delete unreferenced hci_request
> code")
> Signed-off-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
> Cc: Brian Gix <brian.gix@intel.com>
> Cc: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> Cc: Marcel Holtmann <marcel@holtmann.org>
> Cc: Johan Hedberg <johan.hedberg@gmail.com>
> ---
> net/bluetooth/hci_request.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/hci_request.c
> b/net/bluetooth/hci_request.c
> index 5a0296a4352e..f7e006a36382 100644
> --- a/net/bluetooth/hci_request.c
> +++ b/net/bluetooth/hci_request.c
> @@ -269,7 +269,7 @@ void hci_req_add_ev(struct hci_request *req, u16
> opcode, u32 plen,
> void hci_req_add(struct hci_request *req, u16 opcode, u32 plen,
> const void *param)
> {
> - bt_dev_err(req->hdev, "HCI_REQ-0x%4.4x", opcode);
> + bt_dev_dbg(req->hdev, "HCI_REQ-0x%4.4x", opcode);
> hci_req_add_ev(req, opcode, plen, param, 0);
> }
>
>
> base-commit: 094226ad94f471a9f19e8f8e7140a09c2625abaa
Regards,
--Brian Gix
next prev parent reply other threads:[~2022-11-17 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 20:28 [PATCH] Bluetooth: silence a dmesg error message in hci_request.c Mateusz Jończyk
2022-11-16 21:04 ` bluez.test.bot
2022-11-16 21:40 ` [PATCH] " patchwork-bot+bluetooth
2022-11-27 10:57 ` Mateusz Jończyk
2022-11-17 20:34 ` Gix, Brian [this message]
2022-11-17 21:27 ` Mateusz Jończyk
2022-11-17 21:36 ` Gix, Brian
2022-11-17 22:12 ` Luiz Augusto von Dentz
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=499a1278bcf1b2028f6984d61733717a849d9787.camel@intel.com \
--to=brian.gix@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=mat.jonczyk@o2.pl \
--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