From: Oliver Neukum <oneukum@suse.com>
To: weipeng <coderlogicwei@gmail.com>
Cc: anna-maria@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [usb?] INFO: task hung in i2c_tiny_usb_disconnect
Date: Wed, 14 Jan 2026 09:26:54 +0100 [thread overview]
Message-ID: <8bed5082-0aef-4dee-8239-c3e8aba50f9f@suse.com> (raw)
In-Reply-To: <20260114081100.830758-1-coderlogicwei@gmail.com>
Hi,
On 14.01.26 09:11, weipeng wrote:
> I got it. It can be solved by using wait_for_completion in the module exit
> function to wait for all the i2c_tiny_usb_release() to be done.
At that point the module unload would potentially take forever,
because you cannot control how long it takes to complete.
> The i2c_del_adapter() will wait for all the users to put the reference of the adapter.
That seems reasonable.
> It is not a good idea. We can't control the users. So the i2c_del_adapter() can wait
> for any time.
Who exactly takes references? I think at this point you have a design issue
with the i2c layer and seems proper to include the linux-i2c list.
Regards
Oliver
next prev parent reply other threads:[~2026-01-14 8:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 16:32 syzbot
2026-01-12 13:11 ` Wei Peng
2026-01-12 13:24 ` syzbot
2026-01-12 13:31 ` Wei Peng
2026-01-12 13:38 ` Wei Peng
2026-01-12 13:41 ` syzbot
2026-01-13 3:11 ` weipeng
2026-01-13 4:22 ` syzbot
2026-01-13 6:25 ` weipeng
2026-01-13 7:28 ` syzbot
2026-01-13 7:52 ` weipeng
2026-01-13 8:35 ` syzbot
2026-01-13 9:49 ` Oliver Neukum
2026-01-13 15:35 ` weipeng
2026-01-13 15:45 ` weipeng
2026-01-13 15:47 ` weipeng
2026-01-13 16:18 ` syzbot
2026-01-13 20:23 ` Oliver Neukum
2026-01-14 8:11 ` weipeng
2026-01-14 8:26 ` Oliver Neukum [this message]
2026-01-14 8:51 ` weipeng
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=8bed5082-0aef-4dee-8239-c3e8aba50f9f@suse.com \
--to=oneukum@suse.com \
--cc=anna-maria@linutronix.de \
--cc=coderlogicwei@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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®