[Bug 106871] Lower log level for "No Caching mode page found" and "Assuming drive cache: write through"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=106871

--- Comment #1 from Tom Yan <tom.ty89@xxxxxxxxx> ---
https://bugzilla.kernel.org/show_bug.cgi?id=16490#c8

The question is, why are we even using "write through" as fallback when if it
can be dangerous? What's wrong with using "write back" as fallback instead?
Would a SYNCHRONIZE CACHE command ever be a threat to devices without write
cache or caching mode page?

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b81478d82e389dd0961760f5ff6f56b50d29db6d
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=eaa05dfcdb12cf3a7bedf8918dc8699c00944384

Seems like we consider "write back" an safer option everywhere else but we just
somehow require users to use a quirk to switch to that for no reason. This just
looks silly to me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux