| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080218222014.GB31201@elf.ucw.cz> Date: Mon, 18 Feb 2008 23:20:14 +0100 From: Pavel Machek <pavel@....cz> To: Alan Stern <stern@...land.harvard.edu> Cc: kernel list <linux-kernel@...r.kernel.org>, Linux-pm mailing list <linux-pm@...ts.osdl.org> Subject: Re: Status of storage autosuspend 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists