public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric D. Mudama" <edmudama@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Disk write cache (Was: Hyper-Threading Vulnerability)
Date: Tue, 17 May 2005 22:11:19 -0600	[thread overview]
Message-ID: <311601c905051721114040b08a@mail.gmail.com> (raw)
In-Reply-To: <4289652B.7020408@shaw.ca>

On 5/16/05, Robert Hancock <hancockr@shaw.ca> wrote:
> If the power to the drive is truly just cut, then this is basically what
> will happen. However, I have heard, for what it's worth, that in many
> cases if you pull the AC power from a typical PC, the Power Good signal
> from the PSU will be de-asserted, which triggers the Reset line on all
> the buses, which triggers the ATA reset line, which triggers the drive
> to finish writing out the sector it is doing. There is likely enough
> capacitance in the power supply to do that before the voltage drops off.

Yes, but as you said this isn't a power loss event.  It is a hard
reset with a full write cache, which all drives on the market today
respond to by flushing the cache.

According to the spec the time to flush can exceed 30s, so your PSU
better have some honkin caps on it to ensure data integrity when you
yank the power cord out of the wall.

--eric

  reply	other threads:[~2005-05-18  4:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43Bnu-Ut-9@gated-at.bofh.it>
     [not found] ` <44sLm-3Mg-33@gated-at.bofh.it>
     [not found]   ` <44sUX-42h-11@gated-at.bofh.it>
     [not found]     ` <44teb-4fb-1@gated-at.bofh.it>
     [not found]       ` <44uaj-4Z3-5@gated-at.bofh.it>
     [not found]         ` <44LXu-2W6-15@gated-at.bofh.it>
     [not found]           ` <44OVj-5xS-3@gated-at.bofh.it>
     [not found]             ` <44PRr-6mz-33@gated-at.bofh.it>
2005-05-17  3:29               ` Disk write cache (Was: Hyper-Threading Vulnerability) Robert Hancock
2005-05-18  4:11                 ` Eric D. Mudama [this message]
2005-05-18 22:11 Lincoln Dale (ltd)
  -- strict thread matches above, loose matches on Subject: below --
2005-05-18  9:45 Lincoln Dale (ltd)
2005-05-18 13:48 ` John Stoffel
2005-05-18  7:16 Paul Zimmerman
2005-05-18 11:10 ` Richard B. Johnson
2005-05-18 12:47 ` Stephan Wonczak
2005-05-13  5:51 Hyper-Threading Vulnerability Gabor MICSKO
2005-05-13 18:03 ` Andi Kleen
2005-05-13 19:16   ` Diego Calleja
2005-05-15  9:54     ` Andi Kleen
2005-05-15 13:51       ` Mikulas Patocka
2005-05-15 14:12         ` Andi Kleen
2005-05-15 14:52           ` Tomasz Torcz
2005-05-15 15:00             ` Disk write cache (Was: Hyper-Threading Vulnerability) Mikulas Patocka
2005-05-15 15:21               ` Gene Heskett
2005-05-15 15:29                 ` Jeff Garzik
2005-05-16  1:56                   ` Gene Heskett
2005-05-16  2:11                     ` Jeff Garzik
2005-05-16  2:24                     ` Mikulas Patocka
2005-05-16  3:05                       ` Gene Heskett
2005-05-16  2:32                     ` Mark Lord
2005-05-16  3:08                       ` Gene Heskett
2005-05-16 13:44                         ` Mark Lord
2005-05-18  4:03                       ` Eric D. Mudama
2005-05-15 16:24                 ` Mikulas Patocka
2005-05-16 11:18                   ` Matthias Andree
2005-05-16 14:33                     ` Jeff Garzik
2005-05-16 15:26                       ` Richard B. Johnson
2005-05-16 18:11                       ` Valdis.Kletnieks
2005-05-16 14:54                     ` Alan Cox
2005-05-17 13:15                       ` Bill Davidsen
2005-05-17 21:41                         ` Kyle Moffett
2005-05-18  4:06                     ` Eric D. Mudama
2005-05-15 21:38                 ` Tomasz Torcz
2005-05-16 14:50               ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=311601c905051721114040b08a@mail.gmail.com \
    --to=edmudama@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox