From: Alan Stern <stern@rowland.harvard.edu>
To: 朱忠杰 <zhongjiezhu1@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: core: hub: fix usb_hub worker blocking drain_all_pages() worker issue
Date: Mon, 6 Feb 2023 10:17:53 -0500 [thread overview]
Message-ID: <Y+EaIRHZfLs49w9L@rowland.harvard.edu> (raw)
In-Reply-To: <CAJnoMhNYDXjfttiio+P7k6W1fDU3N=jbjmZe+ZRVON=bqm0yvw@mail.gmail.com>
On Mon, Feb 06, 2023 at 11:33:15AM +0800, 朱忠杰 wrote:
> Yes, this is a very special case.
>
> It will happen only when disconnecting the mass storage if there are
> too many files in the storage, and the scanning operation is running,
> and the file system is not unmounted.
> It looks like this issue should be fixed in the usb mass storage
> driver, but I don't find an appropriate place.
That's not surprising, because usb-storage doesn't know anything about
what's happening on the mass-storage device it connects to. All it does
is send the commands that it gets from the SCSI subsystem to the device
and receive the results back. It has no idea whether there is a mounted
filesystem on the device, if the filesystem contains any files, or
whether a scanning operation is running,
A better place to look for fixing this might be the filesystem code.
That's where the information about mounting, files, and scanning can be
found.
Alan Stern
next prev parent reply other threads:[~2023-02-06 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 7:28 [PATCH] USB: core: hub: fix usb_hub worker blocking drain_all_pages() worker issue Zhu Zhongjie
2023-02-03 14:47 ` Alan Stern
2023-02-06 3:33 ` 朱忠杰
2023-02-06 15:17 ` Alan Stern [this message]
2023-02-07 2:02 ` Zhongjie Zhu
2023-02-07 4:07 ` Alan Stern
2023-02-07 8:23 ` Zhongjie Zhu
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=Y+EaIRHZfLs49w9L@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=zhongjiezhu1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox