[Bug 198685] bluez 5.48 memory use after free crash

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

 



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

--- Comment #6 from Luiz Von Dentz (luiz.dentz@xxxxxxxxx) ---
Can you add the output of bluetoothd with debug enabled?

Btw, you don't really need to dup the fd at the client end, at least not with
libdbus, or is this something to do with systemd D-Bus library? Another thing
that stand out is the fact that there is no check for gatt->snd.not, perhaps
the idea is to reacquire on every request? That would be overkill and perhaps
you would be better off using StartNotify instead then. Both bluetoothctl and
meshctl acquire the notification once and just keep it as along as the
connection exists, though if the problem is really the fact that you close and
acquire in quick succession we should fix that since nothing should crash
bluetootd.

-- 
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[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