public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-scsi@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] sd.c fixes applied incorectly to 2.4.19-preXX
Date: Tue, 16 Apr 2002 09:56:50 -0500	[thread overview]
Message-ID: <200204161456.g3GEuo302374@localhost.localdomain> (raw)
In-Reply-To: Message from "Justin T. Gibbs" <gibbs@scsiguy.com> of "Tue, 16 Apr 2002 08:43:43 MDT." <200204161443.g3GEhh990519@aslan.scsiguy.com>

gibbs@scsiguy.com said:
> In my opinion, the only way to really fix the Linux SCSI layer is to
> rip it out and start over using prior art from systems with functional
> I/O subsystems as a guide to building something enterprise worthy.  As
> soon as the community becomes serious about such an endevor, so will
> I. 8-) 

Not perhaps for ripping it up and starting again.  However, there are more 
ways than one to skin a cat.  If you can outline a set of principles, it may 
be possible to move current development towards them.  How about just the five 
worst things about the current subsystem and how we could address them?

> If you insist on doing this, lets at least preserve the current
> behavior:

> 	/*
> 	 * FIXME: this driver treats deferred errors are fatal for
[...]
> 	if (scsi_sense_valid(SCpnt)
> 	 && scsi_sense_key(SCpnt) == SKEY_CURRENT_ERROR) {

Excellent!  It's a lot more readable for people not versed in sense buffer 
layout, thanks!

James


> I don't believe there are definitions to support the second part of
> the if clause, but there could be. 




  reply	other threads:[~2002-04-16 14:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 20:40 [PATCH] sd.c fixes applied incorectly to 2.4.19-preXX Justin T. Gibbs
2002-04-15 20:51 ` James Bottomley
2002-04-15 21:13   ` Justin T. Gibbs
2002-04-16 14:03     ` James Bottomley
2002-04-16 14:43       ` Justin T. Gibbs
2002-04-16 14:56         ` James Bottomley [this message]
2002-04-16 15:25           ` Tony Battersby
2002-04-16 17:36             ` Justin T. Gibbs
2002-04-16 16:18           ` Oliver Xymoron
2002-04-16 17:38             ` Justin T. Gibbs
2002-04-16  5:58 ` Jens Axboe
2002-04-16 14:08   ` Justin T. Gibbs

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=200204161456.g3GEuo302374@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=alan@redhat.com \
    --cc=gibbs@scsiguy.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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