Re: Disk write cache (Was: Hyper-Threading Vulnerability)

>took place on another list, and wrote a test gizmo that copied a
>large file, then slept for 1 second and issued a sync command.  No
>drive led activity until the usual 5 second delay of the filesystem
>had expired.  To me, that indicated that the sync command was being

There's your clue.  The drive LEDs normally reflect activity
over the ATA bus (the cable!). If they're not on, then the drive
isn't receiving data/commands from the host.

Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Disk write cache (Was: Hyper-Threading Vulnerability)
  - From: "Eric D. Mudama" <[email protected]>
- Re: Disk write cache (Was: Hyper-Threading Vulnerability)
  - From: Gene Heskett <[email protected]>

References:
- Hyper-Threading Vulnerability
  - From: Gabor MICSKO <[email protected]>
- Re: Disk write cache (Was: Hyper-Threading Vulnerability)
  - From: Gene Heskett <[email protected]>
- Re: Disk write cache (Was: Hyper-Threading Vulnerability)
  - From: Jeff Garzik <[email protected]>
- Re: Disk write cache (Was: Hyper-Threading Vulnerability)
  - From: Gene Heskett <[email protected]>

Prev by Date: Re: Disk write cache (Was: Hyper-Threading Vulnerability)
Next by Date: Re: {PATCH] Fix IBM EMAC driver ioctl bug
Previous by thread: Re: Disk write cache (Was: Hyper-Threading Vulnerability)
Next by thread: Re: Disk write cache (Was: Hyper-Threading Vulnerability)
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]