From: Marco Pracucci <development@pracucci.com>
To: Dave Young <hidave.darkstar@gmail.com>,
Bluez Development ML <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2.6.23.8: kernel panic
Date: Tue, 27 Nov 2007 16:36:45 +0100 [thread overview]
Message-ID: <474C398D.1000701@pracucci.com> (raw)
In-Reply-To: <20071127103239.GA4477@darkstar.te-china.tietoenator.com>
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.
>
I have applied your patch against kernel 2.6.24-rc3 and I've got the
following error:
Jan 1 00:13:01 user.warn kernel: run_workqueue: recursion depth exceeded: 4
Jan 1 00:13:01 user.warn kernel: [<c0022a88>] (dump_stack+0x0/0x14) from
[<c00485cc>] (run_workqueue+0x4c/0x144)
Jan 1 00:13:01 user.warn kernel: [<c0048580>] (run_workqueue+0x0/0x144)
from [<c00486f8>] (flush_cpu_workqueue+0x34/0x94)
Jan 1 00:13:01 user.warn kernel: r6:c020d624 r5:c05bc088 r4:00000001
Jan 1 00:13:01 user.warn kernel: [<c00486c4>]
(flush_cpu_workqueue+0x0/0x94) from [<c0048cc0>] (flush_workqueue+0x14/0x18)
Jan 1 00:13:01 user.warn kernel: r4:c03c9420
Jan 1 00:13:01 user.warn kernel: [<c0048cac>] (flush_workqueue+0x0/0x18)
from [<c020d640>] (add_conn+0x1c/0x80)
Jan 1 00:13:01 user.warn kernel: [<c020d624>] (add_conn+0x0/0x80) from
[<c0048634>] (run_workqueue+0xb4/0x144)
Jan 1 00:13:01 user.warn kernel: r5:c0340000 r4:c03c9420
Jan 1 00:13:01 user.warn kernel: [<c0048580>] (run_workqueue+0x0/0x144)
from [<c00486f8>] (flush_cpu_workqueue+0x34/0x94)
Jan 1 00:13:01 user.warn kernel: r6:c020d624 r5:c1051e88 r4:00000001
Jan 1 00:13:01 user.warn kernel: [<c00486c4>]
(flush_cpu_workqueue+0x0/0x94) from [<c0048cc0>] (flush_workqueue+0x14/0x18)
Jan 1 00:13:01 user.warn kernel: r4:c03c9420
Jan 1 00:13:01 user.warn kernel: [<c0048cac>] (flush_workqueue+0x0/0x18)
from [<c020d640>] (add_conn+0x1c/0x80)
Jan 1 00:13:01 user.warn kernel: [<c020d624>] (add_conn+0x0/0x80) from
[<c0048634>] (run_workqueue+0xb4/0x144)
Jan 1 00:13:01 user.warn kernel: r5:c0340000 r4:c03c9420
Jan 1 00:13:01 user.warn kernel: [<c0048580>] (run_workqueue+0x0/0x144)
from [<c00486f8>] (flush_cpu_workqueue+0x34/0x94)
Jan 1 00:13:01 user.warn kernel: r6:c020d624 r5:c042ca88 r4:00000001
Jan 1 00:13:01 user.warn kernel: [<c00486c4>]
(flush_cpu_workqueue+0x0/0x94) from [<c0048cc0>] (flush_workqueue+0x14/0x18)
Jan 1 00:13:01 user.warn kernel: r4:c03c9420
Jan 1 00:13:01 user.warn kernel: [<c0048cac>] (flush_workqueue+0x0/0x18)
from [<c020d640>] (add_conn+0x1c/0x80)
Jan 1 00:13:01 user.warn kernel: [<c020d624>] (add_conn+0x0/0x80) from
[<c0048634>] (run_workqueue+0xb4/0x144)
Jan 1 00:13:01 user.warn kernel: r5:c0340000 r4:c03c9420
Jan 1 00:13:01 user.warn kernel: [<c0048580>] (run_workqueue+0x0/0x144)
from [<c0048888>] (worker_thread+0xa4/0xb8)
Jan 1 00:13:01 user.warn kernel: r6:c00487e4 r5:c03c9420 r4:c03c9428
Jan 1 00:13:01 user.warn kernel: [<c00487e4>] (worker_thread+0x0/0xb8)
from [<c004c598>] (kthread+0x5c/0x90)
Jan 1 00:13:01 user.warn kernel: r5:c03c9420 r4:c0340000
Jan 1 00:13:01 user.warn kernel: [<c004c53c>] (kthread+0x0/0x90) from
[<c003b348>] (do_exit+0x0/0x690)
Jan 1 00:13:01 user.warn kernel: r6:00000000 r5:00000000 r4:00000000
Marco Pracucci
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-11-27 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 15:04 [Bluez-devel] 2.6.23.8: kernel panic Marco Pracucci
2007-11-26 6:21 ` Marcel Holtmann
2007-11-27 15:18 ` Marco Pracucci
2007-11-27 10:32 ` Dave Young
2007-11-27 10:38 ` Marcel Holtmann
2007-11-27 10:38 ` Marcel Holtmann
2007-11-27 15:36 ` Marco Pracucci [this message]
2007-11-28 1:33 ` Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=474C398D.1000701@pracucci.com \
--to=development@pracucci.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=hidave.darkstar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.