From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219458] bluetooth connection fails after L2CAP: Fix uaf in l2cap_connect patch
Date: Tue, 12 Nov 2024 02:10:28 +0000 [thread overview]
Message-ID: <bug-219458-62941-5UTMK10rFL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219458-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219458
--- Comment #9 from Pablo Yanez (shaoran@sakuranohana.org) ---
Hi Luiz
Like Guiseppe, on 6.6.58 I didn't revert the original commit and applied the
patch (thus removing only the if clause and the mgmt_device_connected call) and
it seems that the problem is gone.
I was able to connect and disconnect multiple times in succession, I was able
to remove my USB-Bluetooth device and insert it again and was able to connect
again, I tried that several times and it always worked. Now it seems fine.
--
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-11-12 2:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 22:26 [Bug 219458] New: bluetooth connection fails after L2CAP: Fix uaf in l2cap_connect patch bugzilla-daemon
2024-11-05 14:59 ` [Bug 219458] " bugzilla-daemon
2024-11-07 20:46 ` bugzilla-daemon
2024-11-07 20:47 ` bugzilla-daemon
2024-11-07 20:58 ` bugzilla-daemon
2024-11-08 16:31 ` bugzilla-daemon
2024-11-11 14:56 ` bugzilla-daemon
2024-11-12 0:53 ` bugzilla-daemon
2024-11-12 1:18 ` bugzilla-daemon
2024-11-12 2:10 ` bugzilla-daemon [this message]
2024-11-12 18:01 ` bugzilla-daemon
2024-11-18 15:53 ` bugzilla-daemon
2024-11-18 15:53 ` 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-219458-62941-5UTMK10rFL@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.