Commit 394633dd authored May 10, 2024 by Pomai Ahlo

btock_rfc_signaled slot not found error to warning

We see the slot not found error after the corresponding connection has
already been disconnected and cleaned up.  This slot not found error is
often misleading, as it's not the problem.  Reduce to log level to warn
to prevent confusion.

Bug: 295023364
Test: m Bluetooth
Flag: EXEMPT logging change
Change-Id: I4827ffbde4ffa51490c7f85fe94b5e7db86f06de

parent 12e3b0c4

system/btif/src/btif_sock_rfc.cc

+1 −1

Original line number	Diff line number	Diff line
		@@ -950,7 +950,7 @@ void btsock_rfc_signaled(int /* fd */, int flags, uint32_t id) {
		std::unique_lock<std::recursive_mutex> lock(slot_lock);
		rfc_slot_t* slot = find_rfc_slot_by_id(id);
		if (!slot) {
		log::error("RFCOMM slot with id {} not found.", id);
		log::warn("RFCOMM slot with id {} not found.", id);
		return;
		}