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]
Message-ID: <41840b750809171236s524f1a70i3e1624a2facd9d44@mail.gmail.com>
Date:	Wed, 17 Sep 2008 15:36:36 -0400
From:	"Shem Multinymous" <multinymous@...il.com>
To:	"Elias Oltmanns" <eo@...ensachen.de>
Cc:	"Pavel Machek" <pavel@...e.cz>, "Tejun Heo" <tj@...nel.org>,
	"Thomas Renninger" <trenn@...e.de>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"IDE/ATA development list" <linux-ide@...r.kernel.org>
Subject: Re: Laptop shock detection and harddisk protection

On Wed, Sep 17, 2008 at 11:21 AM, Elias Oltmanns <eo@...ensachen.de> wrote:
>>> 2. Make shock protection interact nicely with suspend operations:
>>>    currently, we are out of luck if anything should happen after
>>>    processes have been frozen. This is particularly unfortunatel in the
>>>    case of s2disk.
>>
>> I'd say that s2disk is similar to early boot... no protection there.
>
> Well, this is true for resume. However, I can't help thinking that we
> may do better than that until the disk spins down, particularly while
> writing the image to disk.

Agreed.
Practically, disk protection during suspend-to-disk sounds very
useful, given the typical usage scenario: you press button to
hibernate and start shuffling around your chair/desk in preparation
for leaving the room. Dropping the laptop is more likely than ever at
this point. Resume-from-disk tends to be done after settling down into
your chair/desk, so the drop risk is lower.

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