From: Matthew Wilcox <matthew@wil.cx>
To: Thomas Maguin <T.Maguin@web.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Plextor PowerRec for users
Date: Sun, 12 Feb 2006 12:10:15 -0700 [thread overview]
Message-ID: <20060212191015.GH12822@parisc-linux.org> (raw)
In-Reply-To: <200602121835.44430.T.Maguin@web.de>
On Sun, Feb 12, 2006 at 06:35:24PM +0100, Thomas Maguin wrote:
> On Sunday 12 February 2006 17:53, you wrote:
> > The trouble is that these are vendor-specific commands. So they're safe
> > *for plextor devices*, but they may well be unsafe for other vendors.
> >
> These are just read commands. A correct firmware should just reject the
> commands.
I don't think you understand the point. A non-Plextor device could have
a HALT AND CATCH FIRE command on that opcode. That definitely wouldn't
be safe. If 'just a read command' were enough, we wouldn't need to
have filtering for read commands at all.
> Plextor users have been waiting a long time for the features in linux, so
> please think about a solution which is a solution for all users.
The only solutions I can think of are big and ugly if they're in
the kernel. Why not write a set-uid helper that checks the device
manufacturer and device type, then issues the appropriate command?
That would work on 2.4 as well as 2.6.
next prev parent reply other threads:[~2006-02-12 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 16:18 Plextor PowerRec for users Thomas Maguin
2006-02-12 16:53 ` Matthew Wilcox
2006-02-12 18:47 ` Thomas Maguin
[not found] ` <200602121835.44430.T.Maguin@web.de>
2006-02-12 19:10 ` Matthew Wilcox [this message]
2006-02-12 19:36 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2006-02-12 15:13 Thomas Maguin
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=20060212191015.GH12822@parisc-linux.org \
--to=matthew@wil.cx \
--cc=T.Maguin@web.de \
--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.