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 11:15:49 +0200
From:	"Francesco Pretto" <ceztko@...il.com>
To:	"Rob Landley" <rob@...dley.net>
Cc:	"Dave Jones" <davej@...hat.com>, "Tejun Heo" <htejun@...il.com>,
	"Phillip Susi" <psusi@....rr.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Weird hard disk noise on shutdown (bug #7674)

2007/5/16, Rob Landley <rob@...dley.net>:
> (Is there any other piece of hardware that needs userspace to quiesce it just
> so the _off_switch_ can take effect?  Yes, I read both the gmane thread and
> the linux-ata.org link.  I used to maintain the busybox halt/reboot/poweroff
> commands, although I don't anymore.  That just called reboot(), and this
> worked.)
>

For what i understood, there were a misunderstanding caused by the
wrong assumption that shutdown(8) implementations were issuing
STANDBYNOW on all hard disk devices on the system (indistinctly from
the interface, old-ide/libata/scsi). The fact is that sysvinit and
others actually do something with the old interface /proc/ide, trying
to spindown the hard disks. This worked only on systems using the old
ide/ata drivers because kernel prior to 2.6.22rc1 didn't even have the
necessary feature to spindown hard disks using the libata or the scsi
interface.

Hopefully, with the patch in discussion, there will be an happy ending with:

- sysvinit and derived implementations:
if ( old ide/ata drivers are used )
  {continue to do the old userland spindown mechanism with /proc/ide; }
// else
//  { do nothing; }
reboot();

- everyone else:
// continue to do nothing :-)
reboot();

If exists some, at this point, exotic shutdown(8) implementation that
is trying to issue STANDBYBOW on libata/scsi devices, it will get a
fat warning. The warning could also state that the only supported way
is to leave complete responsibility of spinning down the hard disks to
kernel, so eventually it could be cleaned of checks and compatibility
options.

[1] http://article.gmane.org/gmane.linux.ide/18846
-
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