From: Dave Young <hidden> Date: 2008-01-30 02:23:21
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
---
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
From: David Miller <davem@davemloft.net> Date: 2008-01-30 05:14:39
From: Dave Young <redacted>
Date: Wed, 30 Jan 2008 10:23:54 +0800
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
This looks good, applied, thanks Dave.
I've queued this up for 2.6.25 merging, if you want me to
schedule it for -stable, just let me know.
Thanks again.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
This looks good, applied, thanks Dave.
I've queued this up for 2.6.25 merging, if you want me to
schedule it for -stable, just let me know.
don't include it. I first have to stress test it on one of my machines.
Besides that I have to do some coding style cleanups.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
From: Dave Young <hidden> Date: 2008-01-31 01:29:24
On Jan 30, 2008 6:21 PM, Marcel Holtmann [off-list ref] wrote:
Hi Dave,
quoted
quoted
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
This looks good, applied, thanks Dave.
I've queued this up for 2.6.25 merging, if you want me to
schedule it for -stable, just let me know.
don't include it. I first have to stress test it on one of my machines.
Besides that I have to do some coding style cleanups.
Sorry, I thought you forgot it.
Thanks.
BTW, for the bus_id bug, If there's no urgent need I think we could do
the fix after driver core bus_id changes of kay which will be there
soon.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
---
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
From: Dave Young <hidden> Date: 2008-02-01 01:18:24
On Thu, Jan 31, 2008 at 02:09:30PM +0100, Jens Axboe wrote:
On Wed, Jan 30 2008, Dave Young wrote:
quoted
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
---
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
So you queue &conn->work on both btaddconn and keventd_wq?
My fault. Thanks for pointing out.
new patch as following (some fixes according to marcel's style as well)
---
[PATCH] bluetooth : add conn add/del workqueues to avoid connection fail
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 will warn about same kobject name.
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
---
net/bluetooth/hci_sysfs.c | 52 ++++++++++++++++++++++++++++++++++++----------
1 file changed, 41 insertions(+), 11 deletions(-)
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
From: David Miller <davem@davemloft.net> Date: 2008-02-01 02:33:48
From: Dave Young <redacted>
Date: Fri, 1 Feb 2008 09:24:41 +0800
On Thu, Jan 31, 2008 at 02:09:30PM +0100, Jens Axboe wrote:
quoted
On Wed, Jan 30 2008, Dave Young wrote:
quoted
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
---
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
So you queue &conn->work on both btaddconn and keventd_wq?
My fault. Thanks for pointing out.
new patch as following (some fixes according to marcel's style as well)
Your original patch was already in the tree, so I just checked
in the relative changes.
Please don't me do this next time :-)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
From: Dave Young <hidden> Date: 2008-02-01 02:58:08
On Feb 1, 2008 10:33 AM, David Miller [off-list ref] wrote:
From: Dave Young <redacted>
Date: Fri, 1 Feb 2008 09:24:41 +0800
quoted
On Thu, Jan 31, 2008 at 02:09:30PM +0100, Jens Axboe wrote:
quoted
On Wed, Jan 30 2008, Dave Young wrote:
quoted
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of "same kobject name".
Here add btaddconn & btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young <redacted>
---
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
So you queue &conn->work on both btaddconn and keventd_wq?
My fault. Thanks for pointing out.
new patch as following (some fixes according to marcel's style as well)
Your original patch was already in the tree, so I just checked
in the relative changes.
Please don't me do this next time :-)
David, sorry for it. Should be more careful.
Thanks :)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/