public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-scsi@vger.kernel.org, bugme-new@lists.osdl.org,
	martijn@databoss.nl, "Darrick J. Wong" <djwong@us.ibm.com>,
	Gilbert Wu <Gilbert_Wu@adaptec.com>
Subject: Re: [Bugme-new] [Bug 9018] New: Kernel bug in aic94xx driver shipped with kernel 2.6.21.7
Date: Fri, 14 Sep 2007 17:13:09 -0400	[thread overview]
Message-ID: <46EAF965.1040701@garzik.org> (raw)
In-Reply-To: <20070914135600.67f798e3.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Fri, 14 Sep 2007 07:11:54 -0700 (PDT)
> bugme-daemon@bugzilla.kernel.org wrote:
> 
>> http://bugzilla.kernel.org/show_bug.cgi?id=9018
>>
>>            Summary: Kernel bug in aic94xx driver shipped with kernel
>>                     2.6.21.7
>>            Product: Drivers
>>            Version: 2.5
>>      KernelVersion: 2.6.21.7
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: normal
>>           Priority: P1
>>          Component: Other
>>         AssignedTo: drivers_other@kernel-bugs.osdl.org
>>         ReportedBy: martijn@databoss.nl
>>
>>
>> While rebuilding a MD raid5, every time I try to rebuild:
>>
>> -- START DUMP --
>> RAID5 conf printout:
>>  --- rd:3 wd:2
>>  disk 0, o:1, dev:sdb1
>>  disk 1, o:1, dev:sdc1
>>  disk 2, o:1, dev:sdd1
>> md: recovery of RAID array md0
>> md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
>> md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec)
>> for recovery.
>> md: using 128k window, over a total of 71681920 blocks.
>> ------------[ cut here ]------------
>> kernel BUG at drivers/scsi/aic94xx/aic94xx_hwi.h:354!
> 
> whee!  That's BUG_ON(!list_empty(&ascb->list));
> 
> yet anoher scsi driver with no entry in MAINTAINERS.  Darrick, maybe?

Quite honestly, that's the reality of the situation for (IMO) the 
majority of SCSI drivers.  They just don't really have maintainers at 
all, so it winds up falling onto the subsystem maintainer(s) by default.

Gilbert_Wu@adaptec.com just posted a patch to the driver, so he should 
probably be kept in the loop.

	Jeff



  reply	other threads:[~2007-09-14 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9018-10286@http.bugzilla.kernel.org/>
2007-09-14 20:56 ` [Bugme-new] [Bug 9018] New: Kernel bug in aic94xx driver shipped with kernel 2.6.21.7 Andrew Morton
2007-09-14 21:13   ` Jeff Garzik [this message]
2007-09-14 21:22   ` James Bottomley
2007-09-18 20:14     ` Martijn Prummel

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=46EAF965.1040701@garzik.org \
    --to=jeff@garzik.org \
    --cc=Gilbert_Wu@adaptec.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-new@lists.osdl.org \
    --cc=djwong@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martijn@databoss.nl \
    /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