All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Bryant <nbryant@optonline.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Suspending SCSI devices and buses
Date: Thu, 19 Aug 2004 17:20:09 -0400	[thread overview]
Message-ID: <41251989.3020306@optonline.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0408191647170.2106-100000@ida.rowland.org>

Alan Stern wrote:

> Thanks.  Looking at your patch, I have a question.  It doesn't look like
> the resume path is careful to check for Unit Attention with Power On or
> Medium May Have Changed sense.  What happens if somebody changes the
> medium while the drive is suspended?  Or am I missing something?

I just do the same checks that we do on boot. I suppose if somebody does 
this with a mounted filesystem on removeable media the results might be 
rather comical...

Does "Medium May Have Changed" show up reliably if somebody changes the 
medium in a cartridge drive, Zip drive, etc while it is powered down? 
Doesn't the kernel already notice that sense if it happens during normal 
operation?


Nathan

> 
> Alan Stern
> 
> 


  reply	other threads:[~2004-08-19 21:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 20:36 Suspending SCSI devices and buses Alan Stern
2004-08-18 20:42 ` Christoph Hellwig
2004-08-18 20:49 ` Nathan Bryant
2004-08-19 21:05   ` Alan Stern
2004-08-19 21:20     ` Nathan Bryant [this message]
2004-08-20 12:30     ` Nathan Bryant
2004-08-20 13:35       ` Luben Tuikov
2004-08-20 14:33         ` Nathan Bryant
2004-08-20 15:08       ` Alan Stern
2004-08-20 15:53         ` Nathan Bryant
2004-08-20 16:43           ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2004-08-20 20:49 Pat LaVarre
2004-08-20 21:38 ` Nathan Bryant
2004-08-20 22:06   ` Pat LaVarre
2004-08-20 22:32     ` Nathan Bryant

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=41251989.3020306@optonline.net \
    --to=nbryant@optonline.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.