public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [RFC] sd: make error handling more robust
Date: Mon, 4 Feb 2008 13:02:21 -0800 (PST)	[thread overview]
Message-ID: <134973.94460.qm@web31815.mail.mud.yahoo.com> (raw)
In-Reply-To: <47A72293.8050409@cybernetics.com>

--- On Mon, 2/4/08, Tony Battersby <tonyb@cybernetics.com> wrote:
> I _really_ _really_ hope that you don't believe that I
> am trying to take
> credit for your work. If you take another look, my original
> patch had
> the following hunk:
> 
> +
> +		/* Make sure that bad_lba is one of the sectors that the
> +		 * command was trying to access.
> +		 */
> +		if (bad_lba < start_lba ||
> +		    bad_lba >= start_lba + xfer_size / sector_size)
> +			goto out;
> +
> 
> 
> Your response patch had the following hunk:
> 
> +		if (bad_lba < start_lba)
> +			goto out;
> 
> 
> So I don't feel that it was dishonest for me to submit
> this as "my"
> work. If you were offended, then I apologize.

Oh, no, of course not.  The most important thing is
if it works for you and fixes your problem and makes
your customers happy (or you if you're a customer).

> > I think it would've been much clearer if you had
> > singled out the problems you were seeing with your
> > HW and sent a single problem with a single patch per
> > single email.
> >
> >   
> Agreed. Sometimes it is difficult to predict when something
> that seems
> so straightforward will generate so much controversy.

Nah, maybe a couple of misunderstandings (email tends to
do that), but it's all good.

I think it would've been so much better for everyone if
the RAID vendor had simply fixed their code to not
set VALID when INFORMATION is not valid (spec behaviour).
Since the bug lies in their code, that would've been
the proper course of action.  Instead, every other OS
which uses that RAID HW would have to adjust to this
RAID FW bug (if they haven't already).  Oh, well.

   Luben


  reply	other threads:[~2008-02-04 21:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:24 [PATCH] [RFC] sd: make error handling more robust Luben Tuikov
2008-02-01 11:53 ` Luben Tuikov
2008-02-01 13:44   ` Salyzyn, Mark
2008-02-01 16:15     ` Tony Battersby
2008-02-01 15:46 ` Tony Battersby
2008-02-01 16:09   ` James Bottomley
2008-02-01 20:06   ` Luben Tuikov
2008-02-01 21:02     ` Tony Battersby
2008-02-02  0:49       ` Luben Tuikov
2008-02-04 14:34         ` Tony Battersby
2008-02-04 21:02           ` Luben Tuikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31 21:31 Tony Battersby

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=134973.94460.qm@web31815.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tonyb@cybernetics.com \
    /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