From: Oliver Neukum <oneukum@suse.de>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
hare@suse.de
Subject: Re: [PATCH]SCSI:Do not block suspend for abandoned devices
Date: Wed, 6 Oct 2010 09:22:45 +0200 [thread overview]
Message-ID: <201010060922.45191.oneukum@suse.de> (raw)
In-Reply-To: <1286299186.6661.20.camel@mulgrave.site>
Am Dienstag, 5. Oktober 2010, 19:19:46 schrieb James Bottomley:
> On Tue, 2010-10-05 at 17:21 +0200, Oliver Neukum wrote:
> > From d0e0b88a5b271a45f00ab8ae9f22b992d5d090ba Mon Sep 17 00:00:00 2001
> > From: Oliver Neukum <oliver@neukum.org>
> > Date: Tue, 5 Oct 2010 17:06:46 +0200
> > Subject: [PATCH] SCSI:Do not block suspend for abandoned devices
> >
> > If a device becomes inaccessible while a suspension
> > is carried out, the device is gone anyhow. There's
> > no need to block the suspension, as we'd ignore the
> > devices on later attempts anyway.
>
> So this clarifies what you're trying to do; thanks. However, I still
> think the premise is wrong: if we get a failure for any reason (whether
> memory allocation or disk) we probably haven't flushed the disk cache
> and our next action in suspend (whether to ram or disk) will power the
> drive down and lose the cache data. I really don't think blocking
> suspend and informing the user is inappropriate here.
I see. It seems to me that this is true for SDEV_OFFLINE only.
Regards
Oliver
prev parent reply other threads:[~2010-10-06 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 15:21 [PATCH]SCSI:Do not block suspend for abandoned devices Oliver Neukum
2010-10-05 17:19 ` James Bottomley
2010-10-06 7:22 ` Oliver Neukum [this message]
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=201010060922.45191.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=James.Bottomley@suse.de \
--cc=hare@suse.de \
--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.