| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 27 Nov 2007 11:38:24 +0100 From: Marcel Holtmann <marcel@...tmann.org> To: Dave Young <hidave.darkstar@...il.com> Cc: Marco Pracucci <development@...cucci.com>, bluez-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [Bluez-devel] 2.6.23.8: kernel panic 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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists