From: Tejun Heo <tj@kernel.org>
To: Gwendal Grignou <gwendal@google.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] Do not send RW commands to locked disks.
Date: Thu, 03 Sep 2009 08:03:02 +0900 [thread overview]
Message-ID: <4A9EF9A6.7030404@kernel.org> (raw)
In-Reply-To: <e7510f760909021443m26bee6b9y660f0c5fad89c705@mail.gmail.com>
Hello, Gwendal.
Gwendal Grignou wrote:
> You have a point, but setting the flag LOCKED when an error happen
> will mean that a braindead device [which always trigger
> ata_id_locked()] will work until an internal disk error happens; that
> will make debugging difficult.
Yeah, right, unrelated error can set the LOCKED bit. Maybe we can
devise something intelligent there. A simple state machine to detect
those conditions?
> Instead, I am working on adding the provision for a blacklist to allow
> bad devices to bypass the test.
Blacklist wouldn't be too bad too but I really think we shouldn't be
believing the identify data at the face value. What if the device
sets the bit after security_lock but fails to fail commands which
wouldn't be all that surprising given the general quality of ATA
devices which has been diving rapidly with all those new vendors
jumping onto the SDD wagon? So, I think it should still be something
recognized and verified by EH before applying.
Thanks.
--
tejun
prev parent reply other threads:[~2009-09-02 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 0:28 [PATCH] Do not send RW commands to locked disks Gwendal Grignou
2009-09-02 1:39 ` Tejun Heo
2009-09-02 21:43 ` Gwendal Grignou
2009-09-02 23:03 ` Tejun Heo [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=4A9EF9A6.7030404@kernel.org \
--to=tj@kernel.org \
--cc=gwendal@google.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).