From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jens Axboe <axboe@suse.de>
Cc: "C.Y.M." <syphir@syphir.sytes.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Changes to ide-probe.c in 2.6.9-rc2 causing improper detection
Date: Tue, 14 Sep 2004 11:35:50 +0100 [thread overview]
Message-ID: <1095158149.16520.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20040914111207.GR2336@suse.de>
On Maw, 2004-09-14 at 12:12, Jens Axboe wrote:
> > Drive acked the command is all that proves. Maybe its a nop, maybe it
> > does it, maybe like the last time someone engaged in this kind of "lets
> > not check" approach it erases your firmware and leaves your CD-ROM drive
> > defunct as the Mandrake error of the same form did.
>
> Alan, you are sounding like a broken record :)
Thats because someone else appears incapable of listening and learning
that issuing commands that may not be safe is not a good idea. I happen
to think users should be able to expect their hardware not to go boom
I've nothing against a well documented "actually I have a cache" option
with appropriate warnings (and of course possibly a whitelist if we can
get vendors to help). But one that like hdparm does bother to note when
you may be playing with fire.
Alan
next prev parent reply other threads:[~2004-09-14 11:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 2:26 Changes to ide-probe.c in 2.6.9-rc2 causing improper detection C.Y.M.
2004-09-14 6:06 ` Jens Axboe
2004-09-14 7:03 ` C.Y.M.
2004-09-14 7:06 ` Jens Axboe
2004-09-14 7:15 ` Jens Axboe
2004-09-14 8:20 ` C.Y.M.
2004-09-14 8:28 ` Jens Axboe
2004-09-14 10:09 ` Alan Cox
2004-09-14 11:12 ` Jens Axboe
2004-09-14 10:35 ` Alan Cox [this message]
2004-09-14 11:43 ` Jens Axboe
2004-09-14 11:19 ` Alan Cox
2004-09-14 12:21 ` Jens Axboe
2004-09-14 11:37 ` Gene Heskett
2004-09-14 10:07 ` Alan Cox
2004-09-14 11:11 ` Jens Axboe
2004-09-14 11:59 ` Bartlomiej Zolnierkiewicz
2004-09-14 13:15 ` Jens Axboe
2004-09-14 10:05 ` Alan Cox
2004-09-14 11:09 ` Jens Axboe
2004-09-14 12:07 ` Bartlomiej Zolnierkiewicz
2004-09-14 15:18 ` Jeff Garzik
2004-09-14 15:25 ` Jens Axboe
2004-09-14 15:05 ` Alan Cox
2004-09-14 15:33 ` Mark Lord
2004-09-14 15:39 ` Mark Lord
2004-09-14 15:51 ` Jeff Garzik
2004-09-14 15:06 ` Alan Cox
2004-09-14 15:45 ` Jeff Garzik
2004-09-14 15:31 ` Mark Lord
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=1095158149.16520.24.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=syphir@syphir.sytes.net \
/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