From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: Status of storage autosuspend
Date: Mon, 18 Feb 2008 23:20:14 +0100 [thread overview]
Message-ID: <20080218222014.GB31201@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0802181530330.31135-100000@netrider.rowland.org>
Hi!
> > What is the status of USB storage/SCSI autosuspend patches? They work
> > nicely here ;-).
>
> I could submit them, but there is one outstanding problem I would like
> to solve first. Maybe you can suggest a solution.
>
> The problem is how to handle SG_IOCTL calls. It seems that the only
> safe thing to do is to force an autoresume and prevent the device from
> autosuspending until the device file is closed. Unfortunately the
> SG_IOCTL stuff is all handled inside the block layer, and there's no
> apparent way (other than some dreadful hack) of passing the necessary
> information down to the SCSI layer.
Hmm...
> Should we ignore this issue and submit the patches anyway?
I think you should. "Easy" (and clean) solution to that issue is to
just return -EPERM from SG_IOCTL if autosuspend is configured in ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-02-18 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 20:27 Status of storage autosuspend Pavel Machek
2008-02-18 20:36 ` Alan Stern
2008-02-18 22:20 ` Pavel Machek [this message]
2008-02-19 3:19 ` Alan Stern
2008-02-20 6:20 ` Greg KH
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=20080218222014.GB31201@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox