Re: Status of storage autosuspend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux