[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5vLxmZlxKXfznaWPi2ndxyj90dJN1FML_fINz027uaJP2rZK_nQu_41m7WA7Gnc1yy_XLw8KMWF18Y_keW-qKjHy0BBOQl0A92QiY7Kg004=@proton.me>
Date: Thu, 20 Nov 2025 01:03:52 +0000
From: incogcyberpunk@...ton.me
To: Doug Anderson <dianders@...omium.org>
Cc: Thorsten Leemhuis <regressions@...mhuis.info>, "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>, "marcel@...tmann.org" <marcel@...tmann.org>, "luiz.dentz@...il.com" <luiz.dentz@...il.com>, "linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>, "johan.hedberg@...il.com" <johan.hedberg@...il.com>, "sean.wang@...iatek.com" <sean.wang@...iatek.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] Bluetooth adapter provided by `btusb` not recognized since v6.13.2
Excellant , i will reply to the lore so that further progress from the Bluetooth maintainers can take place.
Also ,
Yes .Simply because this is an unknown territory for me, i had a hard time understanding the problems just from the commit patch message.
I would be grateful if I could understand how the `btmtk_data->isopkt_intf` being NULL caused a crash due to the commit in 6.13.2 and what it means to say `Prior to that
commit we'd pass the NULL pointer directly to
usb_driver_claim_interface() which would detect it and return an
error, which was handled.`.
How was the pointer passed directly such that the device_lock mutex , worked in an undesired manner to lock the adapter and turn it on.
Sorry, for the trouble and the redundancy.
Regards,
IncogCyberpunk
Powered by blists - more mailing lists