public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: Paolo Galtieri <pgaltieri@mvista.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: IPMI panic
Date: Wed, 14 Dec 2005 15:34:05 -0600	[thread overview]
Message-ID: <43A08FCD.2060501@mvista.com> (raw)
In-Reply-To: <1134595930.32485.1.camel@playin.mvista.com>

Yes, there is an error patch that can get here with those values set to
NULL.

Thanks, Paolo.

-Corey

Paolo Galtieri wrote:

>Oops,
>  brain fade - forgot the Signed-of-by.  Resent as requested
>by Corey Minyard.
>
>Folks,
>  while doing some testing I discovered that if the BIOS on a
>board does not properly setup the DMI information it leads to 
>a panic in the IPMI code.  The panic is due to dereferencing 
>a pointer which is not initialized.  The pointer is initialized
>in port_setup() and/or mem_setup() and used in init_one_smi() and
>cleanup_one_si(), however if either port_setup() or mem_setup()
>return ENODEV the pointer does not get initialized.  The patch
>is below done against 2.6.15-rc5-git4
>
>Paolo
>
>Signed-off-by: Paolo Galtieri <pgaltieri@mvista.com>
>
>--- linux-2.6.15-rc5/drivers/char/ipmi/ipmi_si_intf.c	2005-12-05
>10:02:56.000000000 -0700
>+++ new-linux-2.6.15-rc5/drivers/char/ipmi/ipmi_si_intf.c	2005-12-14
>13:57:02.000000000 -0700
>@@ -2399,7 +2399,8 @@
> 			new_smi->handlers->cleanup(new_smi->si_sm);
> 		kfree(new_smi->si_sm);
> 	}
>-	new_smi->io_cleanup(new_smi);
>+	if (new_smi->io_cleanup)
>+		new_smi->io_cleanup(new_smi);
> 
> 	return rv;
> }
>@@ -2518,7 +2519,8 @@
> 
> 	kfree(to_clean->si_sm);
> 
>-	to_clean->io_cleanup(to_clean);
>+	if (to_clean->io_cleanup)
>+		to_clean->io_cleanup(to_clean);
> }
> 
> static __exit void cleanup_ipmi_si(void)
>
>
>  
>


      reply	other threads:[~2005-12-14 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 21:32 IPMI panic Paolo Galtieri
2005-12-14 21:34 ` Corey Minyard [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=43A08FCD.2060501@mvista.com \
    --to=cminyard@mvista.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgaltieri@mvista.com \
    /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