[Bug 219458] bluetooth connection fails after L2CAP: Fix uaf in l2cap_connect patch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=219458

Luiz Von Dentz (luiz.dentz@xxxxxxxxx) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |luiz.dentz@xxxxxxxxx

--- Comment #1 from Luiz Von Dentz (luiz.dentz@xxxxxxxxx) ---
(In reply to Giuseppe Ghibò from comment #0)
> Difficult to track in logs, as logsa are pretty verbose anyway, as even in a
> situation where a connection working there are a lot of warnings; mostly in
> a broken connection with the patch included, logs are like:
> 
> bluetoothd[10741]: Failed to set mode: Failed (0x03)
> bluetoothd[10741]: No matching connection for device
> bluetoothd[10741]: No matching connection for device
> 
> while in a working connection, with the patch reverted, logs are like:
> 
> bluetoothd[10863]: Failed to set mode: Failed (0x03)
> ...
> bluetoothd[10863]: No matching connection for device
> ...
> bluetoothd[10863]: /org/bluez/hci0/dev_<mac_address>/sep2/fd2: fd(42) ready

Could you please attach the btmon trace when this happens?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux