All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 106871] New: Lower log level for "No Caching mode page found" and "Assuming drive cache: write through"
@ 2015-10-29  8:29 bugzilla-daemon
  2015-10-31  8:06 ` [Bug 106871] " bugzilla-daemon
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla-daemon @ 2015-10-29  8:29 UTC (permalink / raw
  To: linux-scsi

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

            Bug ID: 106871
           Summary: Lower log level for "No Caching mode page found" and
                    "Assuming drive cache: write through"
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 4.2.4
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: tom.ty89@gmail.com
        Regression: No

Is there any particular reason that these two should be of error level? I don't
see why we should pay that much of attention to them since it's just how
vendors implemented the drive. Neither can the users or should they do anything
to fix it. IMHO they should be of notice level or at most warning.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug 106871] Lower log level for "No Caching mode page found" and "Assuming drive cache: write through"
  2015-10-29  8:29 [Bug 106871] New: Lower log level for "No Caching mode page found" and "Assuming drive cache: write through" bugzilla-daemon
@ 2015-10-31  8:06 ` bugzilla-daemon
  0 siblings, 0 replies; 2+ messages in thread
From: bugzilla-daemon @ 2015-10-31  8:06 UTC (permalink / raw
  To: linux-scsi

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

--- Comment #1 from Tom Yan <tom.ty89@gmail.com> ---
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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-10-31  8:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-29  8:29 [Bug 106871] New: Lower log level for "No Caching mode page found" and "Assuming drive cache: write through" bugzilla-daemon
2015-10-31  8:06 ` [Bug 106871] " bugzilla-daemon

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.