From: Matthew Wilcox <matthew@wil.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-scsi@vger.kernel.org, Dave Jones <davej@redhat.com>,
Jens Axboe <axboe@suse.de>,
James Bottomley <James.Bottomley@SteelEye.com>,
Douglas Gilbert <dougg@torque.net>
Subject: Re: cd burning with plextor drives.
Date: Sat, 29 Jul 2006 23:57:41 -0600 [thread overview]
Message-ID: <20060730055741.GA4442@parisc-linux.org> (raw)
In-Reply-To: <1154211186.2903.66.camel@laptopd505.fenrus.org>
On Sun, Jul 30, 2006 at 12:13:06AM +0200, Arjan van de Ven wrote:
>
> > (As a historical oddity - there _was_ this bug in some drive that would
> > corrupt the firmware by mistake, though - I think we _did_ actually fry
> > some drives by sending it a "cache flush" command that it wasn't
> > expecting, and that it turned into firmware reload thing or something. I
> > think Alan Cox knows all the gruesome details, but that we could
> > definitely blame on bad hardware..
>
> since you asked for it...
>
> a certain distribution shipped a preproduction version of a packet
> writing patch or it was some barrier thing, I forgot, which would end up
> sending an *ATA* "cache flush" command to ATAPI drives that didn't claim
> to understand that command range. A certain model of cdrom drive (LG?)
> actually had that same command byte code as "flash firmware".
>
> Arguably it's a very stupid value to pick, but it's also not technically
> a drive bug; the drive explicitly claimed to not understand the command
> set in question, and that distro kernel sent it anyway.
Actually, the standard does prohibit these command values from being
reused for different purposes. http://lwn.net/Articles/55815/
next prev parent reply other threads:[~2006-07-30 5:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 4:52 cd burning with plextor drives Dave Jones
2006-07-29 11:12 ` Jens Axboe
2006-07-29 13:40 ` James Bottomley
2006-07-29 15:39 ` Christer Weinigel
2006-07-29 17:06 ` Linus Torvalds
2006-07-29 17:30 ` James Bottomley
2006-07-29 17:49 ` Linus Torvalds
2006-07-30 16:02 ` Christer Weinigel
2006-07-30 19:57 ` Linus Torvalds
2006-07-30 20:18 ` Christian Iversen
2006-07-31 0:12 ` Christer Weinigel
2006-07-31 20:32 ` Linus Torvalds
2006-07-31 20:38 ` Dave Jones
2006-07-31 20:41 ` Jens Axboe
2006-07-31 20:46 ` Linus Torvalds
2006-08-01 6:54 ` Jens Axboe
2006-07-29 18:39 ` Douglas Gilbert
2006-07-29 18:54 ` Linus Torvalds
2006-07-29 20:12 ` Douglas Gilbert
2006-07-29 20:33 ` Linus Torvalds
2006-07-29 20:53 ` Linus Torvalds
2006-07-29 22:13 ` Arjan van de Ven
2006-07-30 5:57 ` Matthew Wilcox [this message]
2006-07-30 9:38 ` Rogier Wolff
2006-07-30 18:02 ` Douglas Gilbert
2006-07-30 20:06 ` Linus Torvalds
2006-07-29 21:40 ` Christer Weinigel
2006-07-30 5:56 ` Linus Torvalds
2006-07-29 17:04 ` Linus Torvalds
2006-07-29 17:22 ` Dave Jones
2006-07-30 10:21 ` Rogier Wolff
2006-07-30 10:31 ` Arjan van de Ven
2006-07-30 11:09 ` Steve McIntyre
2006-07-31 9:33 ` Jens Axboe
2006-07-31 9:32 ` Jens Axboe
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=20060730055741.GA4442@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=arjan@infradead.org \
--cc=axboe@suse.de \
--cc=davej@redhat.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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.