From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: bluez-devel@lists.sourceforge.net, LKML <linux-kernel@vger.kernel.org>
Subject: bluetooth: hci_sysfs work queue problem
Date: Sun, 30 Sep 2007 09:46:38 +0800 [thread overview]
Message-ID: <a8e1da0709291846x4abf50c8g32b02a9d40240b6@mail.gmail.com> (raw)
Hi,
The hci_sysfs uses work queue to finish the sysfs add/del fuction.
But when the same device connection failed, if another connection of
same device come in before the delete work finish, sysfs will warn
about duplicate filename creating.
Sep 19 12:30:27 darkstar kernel: sysfs: duplicate filename
'acl00194FDB6C71' can not be created
Sep 19 12:30:27 darkstar kernel: WARNING: at fs/sysfs/dir.c:433 sysfs_add_one()
Sep 19 12:30:27 darkstar kernel: [<c01c3ad0>] sysfs_add_one+0xa0/0xe0
Sep 19 12:30:27 darkstar kernel: [<c01c3e38>] create_dir+0x48/0xb0
Sep 19 12:30:27 darkstar kernel: [<c0178df5>] __slab_alloc+0x205/0x250
Sep 19 12:30:27 darkstar kernel: [<c01c3ee9>] sysfs_create_dir+0x29/0x50
Sep 19 12:30:27 darkstar kernel: [<c024cf5b>] create_dir+0x1b/0x50
Sep 19 12:30:27 darkstar kernel: [<c024d226>] kobject_add+0x46/0x150
Sep 19 12:30:27 darkstar kernel: [<c024d404>] kobject_set_name+0x84/0xf0
Sep 19 12:30:27 darkstar kernel: [<c02b7035>] device_add+0x95/0x350
Sep 19 12:30:27 darkstar kernel: [<f88aec60>] add_conn+0x0/0x90 [bluetooth]
Sep 19 12:30:27 darkstar kernel: [<f88aec6f>] add_conn+0xf/0x90 [bluetooth]
Sep 19 12:30:27 darkstar kernel: [<c01663d0>] vmstat_update+0x0/0x30
Sep 19 12:30:27 darkstar kernel: [<c013bdfe>] run_workqueue+0x5e/0x110
Sep 19 12:30:27 darkstar kernel: [<c013bf5c>] worker_thread+0xac/0x100
Sep 19 12:30:27 darkstar kernel: [<c0140340>] autoremove_wake_function+0x0/0x50
Sep 19 12:30:27 darkstar kernel: [<c0140340>] autoremove_wake_function+0x0/0x50
Sep 19 12:30:27 darkstar kernel: [<c013beb0>] worker_thread+0x0/0x100
Sep 19 12:30:27 darkstar kernel: [<c013fd49>] kthread+0x59/0xa0
Sep 19 12:30:27 darkstar kernel: [<c013fcf0>] kthread+0x0/0xa0
Sep 19 12:30:27 darkstar kernel: [<c0104fb3>] kernel_thread_helper+0x7/0x14
Sep 19 12:30:27 darkstar kernel: =======================
Sep 19 12:30:27 darkstar kernel: kobject_add failed for
acl00194FDB6C71 with -EEXIST, don't try to register things with the
same name in the same directory.
Sep 19 12:30:27 darkstar kernel: [<c024d2d6>] kobject_add+0xf6/0x150
Sep 19 12:30:27 darkstar kernel: [<c02b7035>] device_add+0x95/0x350
Sep 19 12:30:27 darkstar kernel: [<f88aec60>] add_conn+0x0/0x90 [bluetooth]
Sep 19 12:30:27 darkstar kernel: [<f88aec6f>] add_conn+0xf/0x90 [bluetooth]
Sep 19 12:30:27 darkstar kernel: [<c01663d0>] vmstat_update+0x0/0x30
Sep 19 12:30:27 darkstar kernel: [<c013bdfe>] run_workqueue+0x5e/0x110
Sep 19 12:30:27 darkstar kernel: [<c013bf5c>] worker_thread+0xac/0x100
Sep 19 12:30:27 darkstar kernel: [<c0140340>] autoremove_wake_function+0x0/0x50
Sep 19 12:30:27 darkstar kernel: [<c0140340>] autoremove_wake_function+0x0/0x50
Sep 19 12:30:27 darkstar kernel: [<c013beb0>] worker_thread+0x0/0x100
Sep 19 12:30:27 darkstar kernel: [<c013fd49>] kthread+0x59/0xa0
Sep 19 12:30:27 darkstar kernel: [<c013fcf0>] kthread+0x0/0xa0
Sep 19 12:30:27 darkstar kernel: [<c0104fb3>] kernel_thread_helper+0x7/0x14
Sep 19 12:30:27 darkstar kernel: =======================
Sep 19 12:30:27 darkstar kernel: add_conn: Failed to register connection device
Sep 19 12:41:36 darkstar kernel: [<c0104fb3>] kernel_thread_helper+0x7/0x14
Marcel, how to resolve this problem? do you have some ideas?
Regards
dave
next reply other threads:[~2007-09-30 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 1:46 Dave Young [this message]
2007-10-01 9:45 ` [Bluez-devel] bluetooth: hci_sysfs work queue problem Marcel Holtmann
2007-10-29 3:36 ` 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=a8e1da0709291846x4abf50c8g32b02a9d40240b6@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox