Rob Landley wrote:
>> Yeap, definitely a bug in the kernel and we're trying to fix it. Just
>> for the record, we have _always_ issued FLUSH CACHE, so there hasn't
>> been and won't be any data loss problem. The data loss problem was
>> mentioned as why we can't do things completely inside kernel without
>> updating userland shutdown(8) which issues STANDBYNOW.
>
> Ok, so the change is to get shutdown to _stop_ doing something stupid
> (spinning down the disk without first flushing the cache), and the correct
> thing for shutdown to do is keep its' mitts off the thing and let the kernel
> power down the darn hardware?
Yeah, about right. Because kernel can't skip FLUSH CACHE and FLUSH
CACHE can spin up the disk back again. Oh well, some disks even spin
back up on STANDBYNOW to spin down again. The big fat warning and all
compat mess are to avoid introducing regression and urge shutdown(8)
update such that it does nothing.
--
tejun
-
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/
[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]
