All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Byer <ojbyer@usa.net>
To: linux-scsi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Fw: legacy megaraid driver bug in mm-series
Date: Tue, 13 Sep 2005 06:17:39 -0400	[thread overview]
Message-ID: <4326A743.3060808@usa.net> (raw)



-------- Original Message --------
Subject: Re: Fw: legacy megaraid driver bug in mm-series
Date: Tue, 13 Sep 2005 06:06:29 -0400
From: Jack Byer <ojbyer@usa.net>
To: Christoph Hellwig <hch@infradead.org>
References: <20050907025258.35100c34.akpm@osdl.org>
<20050908143547.GA9741@infradead.org>
<20050909165817.1a8ad251.akpm@osdl.org> <432613BA.5060606@usa.net>
<20050913092359.GA29552@infradead.org>

Christoph Hellwig wrote:
> On Mon, Sep 12, 2005 at 07:48:10PM -0400, Jack Byer wrote:
> 
>>Andrew Morton wrote:
>>
>>>Christoph Hellwig <hch@infradead.org> wrote:
>>>
>>>
>>>>On Wed, Sep 07, 2005 at 02:52:58AM -0700, Andrew Morton wrote:
>>>>
>>>>
>>>>>Begin forwarded message:
>>>>
>>>>This looks preyyu much like a breakage because we're now always sending
>>>>S/G list down the scsi layer.
>>>>
>>>>The patch below brings over code to handle that case from the megaraid_mbox
>>>>driver.  It's still wrong for the case someone sends a MODE_SENSE from
>>>>highmem userspace, but it should at least boot with the patch applied.
>>>>
>>>
>>>
>>>Jack, have you had a chance to test this?
>>>
>>>Thanks.
>>>
>>
>>Sorry, I spent the weekend whitewater rafting :)  I will be able to test
>>this patch on Wednesday. Which kernel versions should I apply this patch to?
> 
> 
> I did it against the at that time latest scsi-misc tree.  The old megaraid
> driver hasn'tt changed much for a long time so it should apply against
> any recent-ish tree.
> 
> 

I tried the patch on a 2.6.13-mm1 tree. It applied cleanly, but produced
a few compiler warnings:


/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c: In function `issue_scb':
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1143: warning: passing
arg 2 of `writel' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c: In function
`issue_scb_block':
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1206: warning: passing
arg 2 of `writel' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1219: warning: passing
arg 2 of `writel' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1221: warning: passing
arg 1 of `readl' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c: In function
`megaraid_isr_memmapped':
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1351: warning: passing
arg 1 of `readl' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1358: warning: passing
arg 2 of `writel' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1377: warning: passing
arg 2 of `writel' makes pointer from integer without a cast
/usr/src/linux-2.6.13-mm1/drivers/scsi/megaraid.c:1381: warning: passing
arg 1 of `readl' makes pointer from integer without a cast

Booting the kernel resulted in the same symptoms as before (can not
mount root fs).


             reply	other threads:[~2005-09-13 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 10:17 Jack Byer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-07  9:52 Fw: legacy megaraid driver bug in mm-series Andrew Morton
2005-09-08 14:35 ` Christoph Hellwig
2005-09-09 23:58   ` Andrew Morton
2005-09-12 23:48     ` Jack Byer
2005-09-13  9:23       ` Christoph Hellwig
     [not found]         ` <4326A4A5.6090200@usa.net>
2005-09-14 18:14           ` Jack Byer

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=4326A743.3060808@usa.net \
    --to=ojbyer@usa.net \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.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.