[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1811141027420.1637-100000@iolanthe.rowland.org>
Date: Wed, 14 Nov 2018 10:35:28 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Martin Petersen <martin.petersen@...cle.com>,
"Zengtao (B)" <prime.zeng@...ilicon.com>
cc: "jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"usb-storage@...ts.one-eyed-alien.net"
<usb-storage@...ts.one-eyed-alien.net>
Subject: RE: scsi_set_medium_removal timeout issue
On Wed, 14 Nov 2018, Zengtao (B) wrote:
> I just enabled the scsi log in the middle of the umount operation, otherwise I can't
> reproduce the issue when the scsi log is enabled.
>
> >from the beginning. In any case, it wasn't what I wanted. I asked you to
> >post the dmesg log, not the SCSI log.
>
> Please refer to the new attachment for dmesg log.
Heh, yes, I see now.
Martin, shouldn't sd_release() call sd_sync_cache() in the same way
that sd_shutdown() does, before it calls scsi_set_medium_removal()?
Alan Stern
Powered by blists - more mailing lists