public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Filippos Papadopoulos <psybases@gmail.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: INITIO scsi driver fails to work properly
Date: Mon, 17 Dec 2007 18:08:59 +0200	[thread overview]
Message-ID: <47669F1B.4090400@panasas.com> (raw)
In-Reply-To: <1197903781.3204.4.camel@localhost.localdomain>

On Mon, Dec 17 2007 at 17:03 +0200, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Mon, 2007-12-17 at 14:36 +0000, Alan Cox wrote:
>> On Mon, 17 Dec 2007 16:40:53 +0200
>> Boaz Harrosh <bharrosh@panasas.com> wrote:
>>
>>> On Mon, Dec 17 2007 at 15:05 +0200, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>>>>> initio doesn't seem to have a maintainer...
>>>>>
>>>>> Are you able to identify any earlier kernel which worked OK?
>>>>>
>>>>> Maybe it's a new device?  If you can get the `lspci -vvxx' output
>>>>> for that device we can take a look.
>>>> If I remember rightly the fixes for this went into the scsi tree a couple
>>>> of months ago. The patch is in the -mm tree as well. No idea why its
>>>> gotten stuck as an obvious one liner.
>>>>
>>>> Alan
>>>> -
>>> You mean this one:
>>> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff;h=ba2c270154cc90c9a8bfc45b7bed4cca78c75aaf
>>>
>>> It's only queued for 2.6.25 via scsi-misc.
>>>
>>> I have found another bug. (See other mail in thread). I Will wait for testing
>>> and submit a proper patch.
>> That one yes - which really should have gone straight into the main tree
>> as the initio driver has been broken all the time it sits queued for
>> future patches. It can't make the problem any worse - the driver does not
>> work.
> 
> Well, the change log isn't very committal for "rush me immediately into
> main line" plus, as far as I could dig out, there was no confirmation
> that it actually worked.  This way, I can now say please try the current
> -mm kernel to the bug reporter and we get to see if this fixes the
> problem.
> 
> James
> 
Below fixes a deadly typo. Might as well be included in 2.6.24
Boaz

--------
>From fdf8ca414f9bb9a5a2cab602991cbac0b128ea65 Mon Sep 17 00:00:00 2001
From: Boaz Harrosh <bharrosh@panasas.com>
Date: Mon, 17 Dec 2007 18:04:11 +0200
Subject: [PATCH] initio: bugfix for accessors patch

  patch: [SCSI] initio: convert to use the data buffer accessors
  had a small but fatal bug. Fixed here.

Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
---
 drivers/scsi/initio.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/scsi/initio.c b/drivers/scsi/initio.c
index 769a7a8..01bf018 100644
--- a/drivers/scsi/initio.c
+++ b/drivers/scsi/initio.c
@@ -2616,6 +2616,7 @@ static void initio_build_scb(struct initio_host * host, struct scsi_ctrl_blk * c
 		scsi_for_each_sg(cmnd, sglist, cblk->sglen, i) {
 			sg->data = cpu_to_le32((u32)sg_dma_address(sglist));
 			total_len += sg->len = cpu_to_le32((u32)sg_dma_len(sglist));
+			++sg;
 		}
 
 		cblk->buflen = (scsi_bufflen(cmnd) > total_len) ?
-- 
1.5.3.3




  reply	other threads:[~2007-12-17 16:08 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9f00bd9d0712170139q1397af5fp3c855a2b94726227@mail.gmail.com>
2007-12-17 11:18 ` INITIO scsi driver fails to work properly Andrew Morton
2007-12-17 11:41   ` Filippos Papadopoulos
2007-12-17 12:18     ` Boaz Harrosh
2007-12-17 12:24       ` Boaz Harrosh
2007-12-19  8:48       ` Filippos Papadopoulos
2007-12-19 10:08         ` Boaz Harrosh
2007-12-19 13:29         ` Matthew Wilcox
2007-12-19 16:50           ` James Bottomley
2007-12-19 17:05             ` Matthew Wilcox
2007-12-20  9:32               ` Natalie Protasevich
2007-12-20 15:08                 ` James Bottomley
2007-12-20 15:14                 ` Theodore Tso
2007-12-21 19:30         ` Chuck Ebbert
2007-12-21 21:03           ` James Bottomley
2007-12-21 22:43             ` Chuck Ebbert
2007-12-21 22:49               ` James Bottomley
2008-01-04  0:18                 ` Filippos Papadopoulos
2008-01-11  5:16                   ` James Bottomley
2008-01-11  9:54                     ` Filippos Papadopoulos
2008-01-11 15:44                       ` James Bottomley
2008-01-11 16:44                         ` Filippos Papadopoulos
2008-01-11 17:01                           ` Alan Cox
2008-01-11 17:33                             ` James Bottomley
2008-01-11 17:01                           ` James Bottomley
2008-01-13 12:28                             ` Filippos Papadopoulos
2008-01-15 15:16                               ` James Bottomley
2008-01-16  5:59                                 ` FUJITA Tomonori
2008-01-16 14:57                                   ` James Bottomley
2008-01-21 22:20                                     ` Alan Cox
2008-01-22 17:50                                       ` Filippos Papadopoulos
2008-01-25 16:49                                         ` James Bottomley
2008-01-25 21:04                                           ` Filippos Papadopoulos
2008-01-11 17:52                         ` Chuck Ebbert
2008-01-11 18:21                           ` Alan Cox
2007-12-17 13:05   ` Alan Cox
2007-12-17 14:40     ` Boaz Harrosh
2007-12-17 14:36       ` Alan Cox
2007-12-17 15:03         ` James Bottomley
2007-12-17 16:08           ` Boaz Harrosh [this message]
2007-12-17 16:20             ` Olivier Galibert
2007-12-17 17:00               ` Boaz Harrosh
2007-12-17 16:13           ` Alan Cox

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=47669F1B.4090400@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=psybases@gmail.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