Hi Dave, > This problem is caused by the workqueue in hci_sysfs.c, the del_conn is > scheduled after the add_conn with same bluetooth address. > > Please try this patch: > ---------------------------- > > The bluetooth hci conn sysfs add/del executed in the default workqueue. If > the conn del function is executed after the new conn add function with same > bluetooth target address, the connection add will failed and warning about > same kobject name. > > Here add a btconn workqueue, and flush the workqueue in the add_conn function > to avoid the above issue.
the patch looks good to me (except some style cleanups). Let me push it to one of my test machines and stress it a little bit. I give you feedback after my testing. Regards Marcel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
