linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@sgi.com>
To: linux-ide@vger.kernel.org
Subject: [PATCH]: [RFC] Fix error handlnig in hwif-init and sgiioc4 driver
Date: Wed, 26 Jan 2005 08:25:04 -0500	[thread overview]
Message-ID: <41F79A30.4040900@sgi.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

I didn't see any ACKs on this so I'm resubmitting....

I discovered an issue where a hwif_init failure lead to /proc/ide files 
being created for devices that failed probes.  This resulted in 
oops/WARN_ON/BUG_ON executions through the kernel depending on what 
actions were on going.

The first part of the fix (submitted to linux-ia64 and acpi-devel for 
review -- I'm including it for completeness) was to fix incorrect error 
handling in the ACPI layer:

===== drivers/acpi/pci_irq.c 1.35 vs edited =====
--- 1.35/drivers/acpi/pci_irq.c 2005-01-04 21:48:17 -05:00
+++ edited/drivers/acpi/pci_irq.c       2005-01-14 08:14:34 -05:00
@@ -487,10 +487,10 @@
        * If no PRT entry was found, we'll try to derive an IRQ from the
        * device's parent bridge.
        */
-       if (!gsi)
+       if (gsi == -1)
               gsi = acpi_pci_irq_derive(dev, pin,
                                         &edge_level, &active_high_low);
-       if (!gsi)
+       if (gsi == -1)
               return_VOID;

       /*

The second part of the fix is to the core IDE layer and to the SGI IOC4 
IDE driver which need to handle errors properly from failed hwif 
initializations.  This patch is attached for review.

[-- Attachment #2: acpi-ide.patch --]
[-- Type: text/plain, Size: 895 bytes --]

===== drivers/ide/ide-probe.c 1.90 vs edited =====
--- 1.90/drivers/ide/ide-probe.c	2004-12-10 14:12:14 -05:00
+++ edited/drivers/ide/ide-probe.c	2005-01-14 08:18:43 -05:00
@@ -841,7 +841,10 @@
 	if (fixup)
 		fixup(hwif);
 
-	hwif_init(hwif);
+	if (!hwif_init(hwif)) {
+		printk("%s: Failed to initialize IDE interface\n", hwif->name);
+		return -1;
+	}
 
 	if (hwif->present) {
 		u16 unit = 0;
===== drivers/ide/pci/sgiioc4.c 1.22 vs edited =====
--- 1.22/drivers/ide/pci/sgiioc4.c	2005-01-06 20:35:35 -05:00
+++ edited/drivers/ide/pci/sgiioc4.c	2005-01-14 08:18:56 -05:00
@@ -669,7 +669,10 @@
 		printk(KERN_INFO "%s: %s Bus-Master DMA disabled\n",
 		       hwif->name, d->name);
 
-	probe_hwif_init(hwif);
+	if (probe_hwif_init(hwif)) {
+		printk(KERN_INFO "%s: initialization failed\n", hwif->name);
+		return -EIO;
+	}
 
 	/* Create /proc/ide entries */
 	create_proc_ide_interfaces(); 

             reply	other threads:[~2005-01-26 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26 13:25 Prarit Bhargava [this message]
2005-02-03 14:46 ` [PATCH]: [RFC] Fix error handlnig in hwif-init and sgiioc4 driver Bartlomiej Zolnierkiewicz
2005-02-08 14:10   ` Prarit Bhargava
2005-02-08 15:53     ` Prarit Bhargava
2005-02-08 16:16       ` Bartlomiej Zolnierkiewicz
2005-02-08 16:49         ` Prarit Bhargava

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=41F79A30.4040900@sgi.com \
    --to=prarit@sgi.com \
    --cc=linux-ide@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).