From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Michael Wu <michael@allwinnertech.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] extcon: Fixed extcon duplicate issue
Date: Mon, 13 Oct 2025 15:32:15 +0900 [thread overview]
Message-ID: <20251013063215epcms1p772dcb340914ecf5f5211dc2fdf052ce6@epcms1p7> (raw)
In-Reply-To: <20251011053719.87055-1-michael@allwinnertech.com>
>extcon_dev_ids may re-alloc to another while this device unregister not complete
>
>The right timing shows below:
>on extcon_dev_register: ida_alloc -> device_register
>on extcon_dev_unregister: device_unregister -> ida_free
>
>stack information when an error occurs:
>sysfs: cannot create duplicate filename '/class/extcon/extcon1'
>CPU: 7 PID: 222 Comm: init Not tainted 6.6.77-android15-8-g9fab1123989e-ab13366090-4k #1 bbfe3ef014a40c2f67534a3e01169790ce021aeb
>Hardware name: sun60iw2 (DT)
>Call trace:
> dump_backtrace+0xe8/0x108
> show_stack+0x18/0x28
> dump_stack_lvl+0x50/0x6c
> dump_stack+0x18/0x24
> sysfs_warn_dup+0x68/0x88
> sysfs_do_create_link_sd+0x94/0xdc
> sysfs_create_link+0x30/0x48
> device_add_class_symlinks+0xb4/0x12c
> device_add+0x1e0/0x48c
> device_register+0x20/0x34
> extcon_dev_register+0x3b8/0x5c4
> devm_extcon_dev_register+0x4c/0x94
>
>Signed-off-by: Michael Wu <michael@allwinnertech.com>
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Cheers,
MyungJoo
prev parent reply other threads:[~2025-10-13 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 5:37 Michael Wu
2025-10-12 17:06 ` Markus Elfring
[not found] ` <CGME20251011061953epcas1p100a774e1790cd78ccfd9f836bb29c693@epcms1p7>
2025-10-13 6:32 ` MyungJoo Ham [this message]
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=20251013063215epcms1p772dcb340914ecf5f5211dc2fdf052ce6@epcms1p7 \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@allwinnertech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®