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

On 5/15/05, Mark Lord <[email protected]> wrote:
> 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.

Mark is correct, activity indicators are associated with bus activity,
not internal drive activity.
-
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/

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]>
- Re: Disk write cache (Was: Hyper-Threading Vulnerability)
  - From: Mark Lord <[email protected]>

Prev by Date: Re: [lm-sensors] Re: [PATCH 2.6.12-rc4 14/15] include/linux/i2c-sysfs.h: i2c sensor_device_attribute and macros
Next by Date: Re: Disk write cache (Was: Hyper-Threading Vulnerability)
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]