[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 #3 from Nathaniel McCallum (npmccallum@xxxxxxxxxx) ---
(In reply to Luiz Von Dentz from comment #1)
> I guess you are calling it from a process that is terminated which cleans up
> the fd before the CCC has been written which is not the way it intended to
> use, it is still a bug though and it shouldn't cause a crash.

No. My process is alive the whole time and doesn't close the file descriptor.
So long as I run bluez under valgrind, the NULL check on gatt-client.c:1437
passes and bluez continues to run and my program continues to receive data. So
I don't understand why characteristic_pipe_hup() is being called at all.

-- 
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