> > the WB
> > caches of IDE devices are not caches in the sense of a MESI cache,
> > they are
> > more like buffer caches and should therefore flush them self after s
> > short
> > period of inactivity without the application of any special flush
> > command.
>
> You now have an absolute vote of *NO CONFIDENCE* on my part. I'm simply
> not going to consider running your code. "It probably wont eat your disk"
> and handwaving is not how you write a block layer.
This is S3/S4 support. Not used during normal operation. S3/S4 without this
is as dangerous as "oops, we've written wrong data to wrong place, without
even knowing that". With this, the problem is "maybe your hdd is not initialized
properly, so you lost ability to talk to it".
> How is anyone supposed to debug file system code in 2.5 when its known
> that it will trash data on some disks anyway ? I'd like to see you cite
It will not. This is only used when ACPI suspend-to-disk/suspend-to-ram
is used (and at that time, you have worse problems than IDE driver).
Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/