All of lore.kernel.org
 help / color / mirror / Atom feed
From: weipeng <coderlogicwei@gmail.com>
To: oneukum@suse.com
Cc: anna-maria@linutronix.de, coderlogicwei@gmail.com,
	frederic@kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org,
	syzbot+30b78308ba7e64647ff8@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [usb?] INFO: task hung in i2c_tiny_usb_disconnect
Date: Tue, 13 Jan 2026 23:35:47 +0800	[thread overview]
Message-ID: <20260113153547.335916-1-coderlogicwei@gmail.com> (raw)
In-Reply-To: <30e2487e-5738-46bc-95f7-8d0ba3ba9b1a@suse.com>

On Tue, 13 Jan 2026 10:49:16, Oliver Neukum wrote:

> For once what prevents the driver from being unloaded
> with a work item queued after disconnect() has run?
> How do you make sure that the disconnected flag is ever read?

Hi,

Did you say that we can't make sure the usb_read() and usb_write()
is prevented after the dev->disconnected is set to true?
It is indeed a problem. I will send a new patch soon.

Thanks for review!

  reply	other threads:[~2026-01-13 15:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 16:32 [syzbot] [usb?] INFO: task hung in i2c_tiny_usb_disconnect 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 [this message]
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
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=20260113153547.335916-1-coderlogicwei@gmail.com \
    --to=coderlogicwei@gmail.com \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=syzbot+30b78308ba7e64647ff8@syzkaller.appspotmail.com \
    --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 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.