From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218651] kernel 6.8.2 - Bluetooth bug/dump at boot
Date: Sat, 30 Mar 2024 01:49:57 +0000 [thread overview]
Message-ID: <bug-218651-62941-yGKclWMVgN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218651-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218651
sugaraddicted@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sugaraddicted@gmail.com
--- Comment #10 from sugaraddicted@gmail.com ---
Here is the bisect.
$ git bisect good
b53e5ef62fe9853648b4478bd6cb3aba970a6f1f is the first bad commit
commit b53e5ef62fe9853648b4478bd6cb3aba970a6f1f
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
[ Upstream commit 63298d6e752fc0ec7f5093860af8bc9f047b30c8 ]
If command has timed out call __hci_cmd_sync_cancel to notify the
hci_req since it will inevitably cause a timeout.
This also rework the code around __hci_cmd_sync_cancel since it was
wrongly assuming it needs to cancel timer as well, but sometimes the
timers have not been started or in fact they already had timed out in
which case they don't need to be cancel yet again.
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Stable-dep-of: 2615fd9a7c25 ("Bluetooth: hci_sync: Fix overwriting request
callback")
Signed-off-by: Sasha Levin <sashal@kernel.org>
include/net/bluetooth/hci_sync.h | 2 +-
net/bluetooth/hci_core.c | 84 +++++++++++++++++++++++++++-------------
net/bluetooth/hci_request.c | 2 +-
net/bluetooth/hci_sync.c | 20 +++++-----
net/bluetooth/mgmt.c | 2 +-
5 files changed, 71 insertions(+), 39 deletions(-)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-03-30 1:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 2:10 [Bug 218651] New: kernel 6.8.2 - Bluetooth bug/dump at boot bugzilla-daemon
2024-03-28 2:12 ` [Bug 218651] " bugzilla-daemon
2024-03-28 2:13 ` bugzilla-daemon
2024-03-28 11:00 ` bugzilla-daemon
2024-03-28 11:03 ` bugzilla-daemon
2024-03-28 11:08 ` bugzilla-daemon
2024-03-28 12:48 ` bugzilla-daemon
2024-03-28 12:49 ` bugzilla-daemon
2024-03-28 12:50 ` bugzilla-daemon
2024-03-28 12:52 ` bugzilla-daemon
2024-03-30 1:49 ` bugzilla-daemon [this message]
2024-03-30 1:50 ` bugzilla-daemon
2024-03-30 13:59 ` bugzilla-daemon
2024-03-30 15:50 ` bugzilla-daemon
2024-03-30 17:27 ` bugzilla-daemon
2024-03-30 19:34 ` bugzilla-daemon
2024-03-30 21:52 ` bugzilla-daemon
2024-03-31 15:48 ` bugzilla-daemon
2024-03-31 16:21 ` bugzilla-daemon
2024-03-31 16:56 ` bugzilla-daemon
2024-04-01 20:33 ` bugzilla-daemon
2024-04-02 6:47 ` bugzilla-daemon
2024-04-04 4:45 ` bugzilla-daemon
2024-04-04 5:38 ` bugzilla-daemon
2024-04-04 8:56 ` bugzilla-daemon
2024-04-05 16:35 ` bugzilla-daemon
2024-04-06 6:54 ` bugzilla-daemon
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=bug-218651-62941-yGKclWMVgN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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 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.