Hi Florian, On Fri, Jun 26, 2015 at 3:36 PM, jerico.dev <jerico.dev@xxxxxxxxx> wrote: > > > On 06/26/2015 02:28 PM, Luiz Augusto von Dentz wrote: >> >> Hi Florian, >> >> On Fri, Jun 26, 2015 at 3:22 PM, jerico.dev <jerico.dev@xxxxxxxxx> wrote: >>> >>> Hi Luiz, >>> >>>>>> Any way, once I run the example-advertisement script, I cannot run it >>>>>> again until I restart the bleutooth daemon. >>>>>> This is known issue. >>>>> >>>>> >>>>> >>>>> Okay, I'll keep digging. >>>> >>>> >>>> >>>> That is something in the kernel Im afraid, it doesn't seems to remove >>>> the instances properly. >>> >>> >>> >>> is it possible to reproduce this bad behavior with the btmgmt tool? I'd >>> like >>> to have a look at it to find out the reason. >> >> >> Check the patch I just sent. > > > Nice. So in fact it was just invalid instance ids being used. What about the > instance removal issue, did that materialize somehow? It was not an issue actually, the instance is removed it just that the userspace has to remember which id are available, Im not sure this is a good idea though, it seems anyone can overwrite the instance id adding its own data provided it has access to mgmt socket. -- Luiz Augusto von Dentz -- 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
