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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 May 2007 23:05:11 -0400
From:	Rob Landley <rob@...dley.net>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Tejun Heo <htejun@...il.com>, Dave Jones <davej@...hat.com>,
	Francesco Pretto <ceztko@...il.com>,
	Phillip Susi <psusi@....rr.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Weird hard disk noise on shutdown (bug #7674)

On Wednesday 16 May 2007 8:58 pm, Henrique de Moraes Holschuh wrote:
> On Wed, 16 May 2007, Rob Landley wrote:
> > Ok, so the change is to get shutdown to _stop_ doing something stupid 
> > (spinning down the disk without first flushing the cache), and the correct 
> > thing for shutdown to do is keep its' mitts off the thing and let the 
kernel 
> > power down the darn hardware?
> 
> Yes, for *all* SCSI disk devices, libata or not.

I realize that this time next year it won't be possible to use a ramdisk or a 
network block device without going through the SCSI layer, but while it 
remains an option I'm relishing _not_ using it, thanks.

> But you need to detect if the kernel has proper SCSI device shutdown
> support, because if it does not, you have to do a cache flush and spindown
> on shutdown(8) if you can...

Or (and this is just a thought), you could upgrade your kernel so it correctly 
handles your hardware, treating this just like any other driver bug or other 
lack of proper hardware support in the history of Linux.  (Back when APM 
couldn't power off the machine at the end of the shutdown sequence, did we 
modify shutdown to try to work around this, or did we fix it in the kernel so 
it worked?)

Why does everybody want to shoehorn everything through the SCSI layer, anyway?  
Last I checked you didn't have to spin down a USB flash key.  If SATA is 
SCSI, what the heck is SAS?  (Answer: a cynical marketing hack to bleed SCSI 
bigots for the huge margins they've always been bled for.  But oh well.)  It 
would be hilarious if I didn't have to put up with it renumbering my devices 
and imposing requirements for hardware I haven't got on hardware I have 
got...

Rob
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ