From: Kenji Kaneshige <kaneshige.kenji-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
To: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Kenji Kaneshige
<kaneshige.kenji-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Subject: [PATCH 2.6.13-rc4 2/2] fix possible null pointer access - acpi_pci_irq_disable
Date: Mon, 01 Aug 2005 12:35:50 +0900 [thread overview]
Message-ID: <42ED9896.7080709@jp.fujitsu.com> (raw)
In-Reply-To: <42ED97C2.7060409-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
This patch fixes possible null pointer access in acpi_pci_irq_disable.
The 'bus' field in pci_dev structure should be checked before calling
pci_read_config_byte() because pci_bus_read_config_byte() called by
pci_read_config_byte() refers to 'bus' field.
Signed-off-by: Kenji Kaneshige <kaneshige.kenji-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
---
drivers/acpi/pci_irq.c | 5 +----
1 files changed, 1 insertion(+), 4 deletions(-)
diff -puN drivers/acpi/pci_irq.c~fix-possible-null-pointer-access-acpi_pci_irq_disable drivers/acpi/pci_irq.c
--- linux-2.6.13-rc4/drivers/acpi/pci_irq.c~fix-possible-null-pointer-access-acpi_pci_irq_disable 2005-08-01 12:20:31.000000000 +0900
+++ linux-2.6.13-rc4-kanesige/drivers/acpi/pci_irq.c 2005-08-01 12:20:31.000000000 +0900
@@ -474,7 +474,7 @@ acpi_pci_irq_disable (
ACPI_FUNCTION_TRACE("acpi_pci_irq_disable");
- if (!dev)
+ if (!dev || !dev->bus)
return_VOID;
pci_read_config_byte(dev, PCI_INTERRUPT_PIN, &pin);
@@ -482,9 +482,6 @@ acpi_pci_irq_disable (
return_VOID;
pin--;
- if (!dev->bus)
- return_VOID;
-
/*
* First we check the PCI IRQ routing table (PRT) for an IRQ.
*/
_
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
prev parent reply other threads:[~2005-08-01 3:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 3:32 [PATCH 2.6.13-rc4 0/2] fix possible null pointer access in acpi_pci_irq_{enable, disable} Kenji Kaneshige
[not found] ` <42ED97C2.7060409-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-08-01 3:34 ` [PATCH 2.6.13-rc4 1/2] fix possible null pointer access - acpi_pci_irq_enable Kenji Kaneshige
[not found] ` <42ED9830.7060808-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-08-03 11:36 ` Pavel Machek
[not found] ` <20050803113637.GB4038-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-08-05 1:34 ` Kenji Kaneshige
[not found] ` <42F2C20F.4050807-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-08-05 7:19 ` Pavel Machek
[not found] ` <20050805071918.GG1780-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-08-08 4:24 ` Kenji Kaneshige
[not found] ` <42F6DE69.5090101-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-08-08 5:07 ` Andrew Morton
2005-08-01 3:35 ` Kenji Kaneshige [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=42ED9896.7080709@jp.fujitsu.com \
--to=kaneshige.kenji-+cum20s59erqfuhtdcdx3a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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