public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Andre Tomt <andre@tomt.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-rc4 - pls test (and no more patches)
Date: Mon, 11 Oct 2004 21:01:25 -0400	[thread overview]
Message-ID: <1097542884.1453.120.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0410111633410.3897@ppc970.osdl.org>

On Mon, 2004-10-11 at 19:35, Linus Torvalds wrote:
> Well, as far as I can tell from the patch, the only way to get data 
> corruption from the bug is when you use the SCSI ioctl's at the same time 
> as the disk is busy.
> 
> In other words, I think you'd have to do some special disk management, or
> possibly try to burn a CD on a SCSI CD-ROM (or other special device that
> uses the SCSI ioctl's) on the same controller. And nobody uses SCSI
> CD-burners any more, I'd think.

This is not some far-out scenario.  For a long time Plextor SCSI burners
were the best on the market, there are 1000's of them out there.

Lee


  reply	other threads:[~2004-10-12  1:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11  3:22 Linux 2.6.9-rc4 - pls test (and no more patches) Linus Torvalds
2004-10-11  7:07 ` Gene Heskett
2004-10-11  7:23 ` via-velocity heads up (was (Re: Linux 2.6.9-rc4 - pls test (and no more patches)) Francois Romieu
2004-10-11 13:32   ` Daniel Andersen
2004-10-11 16:53   ` Jerone Young
2004-10-11  9:07 ` Linux 2.6.9-rc4 - pls test (and no more patches) Brice Goglin
2004-10-11 14:57   ` Linus Torvalds
2004-10-11 20:22     ` Kjartan Maraas
2004-10-11  9:35 ` Andre Tomt
2004-10-11 15:02   ` Linus Torvalds
2004-10-11 15:09     ` James Bottomley
2004-10-11 18:22       ` Andre Tomt
2004-10-11 19:29         ` James Bottomley
2004-10-11 23:35           ` Linus Torvalds
2004-10-12  1:01             ` Lee Revell [this message]
2004-10-12  4:02             ` William Lee Irwin III
2004-10-12  6:57             ` Jesper Juhl
2004-10-11 21:37       ` Chris Ricker
2004-10-11  9:54 ` Nick Piggin
2004-10-11 15:17   ` Linus Torvalds
2004-10-11 15:25     ` Linus Torvalds
2004-10-12  0:11       ` Nick Piggin
2004-10-11 23:48     ` Nick Piggin
2004-10-12  6:00       ` Barry K. Nathan
2004-10-11 15:48 ` Linux 2.6.9-rc4 (compile stats) John Cherry
2004-10-11 15:51   ` John Cherry
2004-10-11 16:24 ` [patch] 2.6.9-rc4: SCSI qla2xxx gcc 3.4 compile errors Adrian Bunk
2004-10-11 16:28   ` James Bottomley
2004-10-11 16:35     ` Adrian Bunk
2004-10-11 17:05       ` James Bottomley
2004-10-11 22:04 ` Linux 2.6.9-rc4 - pls test (and no more patches) Tom Rini
2004-10-11 23:23   ` Tom Rini
2004-10-12  8:05 ` Matthias Andree
2004-10-12  9:09   ` [PATCH] tcp_output.c: tcp_set_skb_tso_factor ---> tcp_set_skb_tso_segs [Was: Re: Linux 2.6.9-rc4 - pls test (and no more patches)] Sami Farin
  -- strict thread matches above, loose matches on Subject: below --
2004-10-11 16:07 Linux 2.6.9-rc4 - pls test (and no more patches) Yu, Luming

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=1097542884.1453.120.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andre@tomt.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox