Hi Andrew,
Am 06.07.19 um 18:09 schrieb Andrew Lunn:
> On Sat, Jul 06, 2019 at 05:18:59PM +0200, jo...@solid-run.com wrote:
>> From: Josua Mayer
>>
>> Print a warning when device tree specifies more than the maximum of four
>> clocks supported by orion-mdio. Because re
5
>> ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
>
> The free and use-after-free are both via the same do_enable_set() path
> which implies there are racing writes to the debugfs write handler. It
> seems locking is missing for both listen_chan and enable_6lowpan. The
> latter seems misused in is_bt_6lowpan(), which should likely just be
> checking for chan->ops == &bt_6lowpan_chan_ops, I think?
>
> I have no way to actually test changes to this code...
>
I do have limited hardware for testing bluetooth 6lowpan connections,
but am a little busy these weeks. So some time by the end of this month
I should be able to at least verify if my use-case would be broken by a
change, if somebody were to propose one ;)
br
Josua Mayer
