All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 106871] Lower log level for "No Caching mode page found" and "Assuming drive cache: write through"
Date: Sat, 31 Oct 2015 08:06:05 +0000	[thread overview]
Message-ID: <bug-106871-11613-Cv2D6tS5IV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106871-11613@https.bugzilla.kernel.org/>

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.

      reply	other threads:[~2015-10-31  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106871-11613-Cv2D6tS5IV@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.