From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] iosapic.c NULL pointer deref
Date: Thu, 19 Oct 2000 17:38:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205598@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205597@msgid-missing>
Matt,
This code was put in specifically for AMI MegaRaid controller and bridge
cards. Mike from Intel did the patch. Anyway, I am working on the IOSAPIC
code to fix a problem and would like to fix this problem also. Please let me
know if you have any suggestion.
Thanks,
Asit
> -----Original Message-----
> From: Matt_Domsch@Dell.com [mailto:Matt_Domsch@Dell.com]
> Sent: Wednesday, October 18, 2000 3:12 PM
> To: linux-ia64@linuxia64.org
> Cc: peterj@ami.com
> Subject: [Linux-ia64] iosapic.c NULL pointer deref
>
>
> In the 2.4.0-test8 and -test9 IA-64 patch, the file
> arch/ia64/dig/iosapic.c,
> function pci_for_each_dev(), the bridge pointer can be NULL, but gets
> dereferenced anyhow, causing a nice tombstone. I see this with an AMI
> MegaRAID 471 card that happens to have two bridges on it.
> Putting in tests
> against NULL, that routine doesn't blow up any longer, but
> interrupts are
> not properly assigned to that card then, and eventually all SCSI
> reads/writes time out.
>
> I'm happy to work with whomever is responsible for this code
> to have it
> properly assign interrupts to these cards.
>
> Thanks,
> Matt
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
prev parent reply other threads:[~2000-10-19 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-18 22:11 [Linux-ia64] iosapic.c NULL pointer deref Matt_Domsch
2000-10-19 17:38 ` Mallick, Asit K [this message]
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=marc-linux-ia64-105590678205598@msgid-missing \
--to=asit.k.mallick@intel.com \
--cc=linux-ia64@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