From: Eric Valette <eric.valette@free.fr>
To: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: your recently submitted patch to fix BT RIP error shall be applied to 6.6 stable (I have a systematic crash on reboot in 6.6.23)
Date: Wed, 27 Mar 2024 14:46:47 +0100 [thread overview]
Message-ID: <608ed80b-89dd-4815-84ed-5a03abc19c17@free.fr> (raw)
In-Reply-To: <8a6d3251-f7ae-4b10-956c-7d24a45464f5@free.fr>
On 27/03/2024 14:41, Eric Valette wrote:
> On 27/03/2024 14:36, Von Dentz, Luiz wrote:
>> Hi Eric,
>>
>> This shouldn't apply to 6.6 kernel, the regression was introduced with:
>>
>> commit 711c35949648ba19f54bce27b49ced0ad90b19b9
>> Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>> Date: Tue Jan 9 13:45:40 2024 -0500
>>
>> Bluetooth: hci_core: Cancel request on command timeout
>>
>> So, you only really need that fix if you were using 6.9-rc1
>
> Well I get the same error message and with the fix it works again.
>
> Will check the 6.6.22 6.6.23 patch.
>
> Could you point me to the problematic patch via adiff that I could
> easilly check?
Found it. The patch adds the function hci_send_cmd_sync and I have it in
my 6.6.23 kernel tree.
grep hci_send_cmd_sync net/bluetooth/hci_core.c
static void hci_send_cmd_sync(struct hci_dev *hdev, struct sk_buff *skb)
hci_send_cmd_sync(hdev, skb);
more Makefile
# SPDX-License-Identifier: GPL-2.0
VERSION = 6
PATCHLEVEL = 6
SUBLEVEL = 23
EXTRAVERSION =
-- eric
next prev parent reply other threads:[~2024-03-27 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 13:14 Eric Valette
[not found] ` <PH0PR11MB512628ED33CB0EC120ECC08AD3342@PH0PR11MB5126.namprd11.prod.outlook.com>
2024-03-27 13:41 ` Eric Valette
2024-03-27 13:46 ` Eric Valette [this message]
[not found] ` <PH0PR11MB5126D61336DDE016C3607997D3342@PH0PR11MB5126.namprd11.prod.outlook.com>
2024-03-27 14:10 ` Eric Valette
2024-03-27 16:37 ` Eric Valette
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=608ed80b-89dd-4815-84ed-5a03abc19c17@free.fr \
--to=eric.valette@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.von.dentz@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®