From: Diffie <diffie@blazebox.homeip.net>
To: Mike Anderson <andmike@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Sat, 2 Aug 2003 01:57:16 -0400 [thread overview]
Message-ID: <20030802055716.GC3613@blazebox.homeip.net> (raw)
In-Reply-To: <20030801232721.GA5249@beaverton.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
On Fri, Aug 01, 2003 at 04:27:22PM -0700, Mike Anderson wrote:
> Andrew Morton [akpm@osdl.org] wrote:
> > This patch should fix the oops.
> >
> > As for why the proc reading code was unable to locate the HBA: dunno, but
> > this is a first step.
> >
> > Or maybe you don't have any adaptec controllers in the machine?
> >
> > (jejb, please apply..)
> >
> >
> > 25-akpm/drivers/scsi/aic7xxx_old/aic7xxx_proc.c | 2 +-
> > 1 files changed, 1 insertion(+), 1 deletion(-)
> >
> > diff -puN drivers/scsi/aic7xxx_old/aic7xxx_proc.c~aic7xxx_old-oops-fix drivers/scsi/aic7xxx_old/aic7xxx_proc.c
> > --- 25/drivers/scsi/aic7xxx_old/aic7xxx_proc.c~aic7xxx_old-oops-fix Fri Aug 1 14:41:14 2003
> > +++ 25-akpm/drivers/scsi/aic7xxx_old/aic7xxx_proc.c Fri Aug 1 14:41:20 2003
> > @@ -92,7 +92,7 @@ aic7xxx_proc_info ( struct Scsi_Host *HB
> >
> > HBAptr = NULL;
> >
> > - for(p=first_aic7xxx; p->host != HBAptr; p=p->next)
> > + for(p=first_aic7xxx; p && p->host != HBAptr; p=p->next)
> > ;
> >
> > if (!p)
>
> Is this really the right thing to add. The only purpose of these few lines
> is a poor sanity check as down further in the code a pointer to the
> structure is already present in hostdata.
>
> Adding the "p" is an indication that this drivers list got corrupted some
> where.
>
> I agree it may be better than an oops, but what else is invalid?
>
> You need to have adaptec controllers in the system to get a procfs node
> to read / write, but this error could be related to the node not getting
> cleaned up correctly on a remove which a patch has previously been
> posted.
>
> -andmike
> --
> Michael Anderson
> andmike@us.ibm.com
>
>
Mike,
I do indeed have an AHA-2940U2W controller in the box...could you be
kind and point me at the said patch? Thank you.
Regards,
Paul
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-02 5:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 18:22 Badness in device_release at drivers/base/core.c:84 Diffie
2003-08-01 21:27 ` Greg KH
2003-08-02 5:40 ` Diffie
2003-08-01 21:44 ` Andrew Morton
2003-08-01 23:27 ` Mike Anderson
2003-08-02 5:57 ` Diffie [this message]
2003-08-02 5:53 ` Diffie
2003-08-03 1:55 ` Diffie
2003-08-03 2:07 ` Andrew Morton
2003-08-03 21:47 ` Diffie
2003-08-03 21:52 ` Andrew Morton
2003-08-03 22:23 ` Diffie
2003-08-03 22:31 ` Diffie
2003-08-04 16:30 ` Patrick Mansfield
2003-08-04 17:48 ` Paul Blazejowski
2003-08-04 18:26 ` Paul Blazejowski
2003-08-04 18:57 ` Patrick Mansfield
2003-08-04 19:36 ` Justin T. Gibbs
2003-08-05 2:21 ` Paul Blazejowski
2003-08-05 10:20 ` wb
2003-08-05 16:10 ` Ishikawa
2003-08-06 16:58 ` Paul Blazejowski
2003-08-06 17:20 ` Chiaki
2003-08-13 2:03 ` Chiaki
2003-08-06 16:55 ` Paul Blazejowski
2003-08-05 7:18 ` Paul Blazejowski
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=20030802055716.GC3613@blazebox.homeip.net \
--to=diffie@blazebox.homeip.net \
--cc=andmike@us.ibm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).