| 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
| ||
|
Date: Fri, 07 Mar 2008 09:13:06 +0900 From: Tejun Heo <htejun@...il.com> To: James Bottomley <James.Bottomley@...senPartnership.com> CC: Mark Lord <liml@....ca>, Matthew Wilcox <matthew@....cx>, linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org> Subject: Re: ata_ram driver James Bottomley wrote: >> * Driver unload: Dealt the same way as hot unplugging. > > This is the problem case: driver unloading should have a > scsi_remove_host() in its path. This is the trigger that sends out the > flushes/stops and calls slave_destroy. scsi_remove_host() doesn't > actually return until all the destroys are completed, so it makes module > unloading wait until everything is properly shut down. > >> Making driver unload like explicit unplug request is possible but it >> will mean that drives will be spun down on driver unload, which can be >> annoying to developers. > > You have a sysfs flag to prevent that, don't you? Yeap, sure. It's the combination of things that always made me put this off. Is there a function I can call to just shutdown the host instead of destroying it? Thanks. -- tejun -- 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