public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] trival: fix acpi_hest_firmware_first_pci() caused oops
Date: Tue, 20 Apr 2010 11:01:21 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1004201100220.2402@sony> (raw)
In-Reply-To: <1270696575-3385-1-git-send-email-shaohua.li@intel.com>

wouldn't it be better for acpi_get_table()
to return failure for acpi=off?

thanks,
Len Brown, Intel Open Source Technology Center

On Thu, 8 Apr 2010, Shaohua Li wrote:

> acpi_hest_firmware_first_pci() could be called when acpi is disabled
> and cause system oops.
> 
> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> ---
>  drivers/acpi/hest.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/acpi/hest.c b/drivers/acpi/hest.c
> index 4bb18c9..1c527a1 100644
> --- a/drivers/acpi/hest.c
> +++ b/drivers/acpi/hest.c
> @@ -123,6 +123,10 @@ int acpi_hest_firmware_first_pci(struct pci_dev *pci)
>  {
>  	acpi_status status = AE_NOT_FOUND;
>  	struct acpi_table_header *hest = NULL;
> +
> +	if (acpi_disabled)
> +		return 0;
> +
>  	status = acpi_get_table(ACPI_SIG_HEST, 1, &hest);
>  
>  	if (ACPI_SUCCESS(status)) {
> -- 
> 1.6.3.3
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2010-05-01  1:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  3:16 [PATCH] trival: fix acpi_hest_firmware_first_pci() caused oops Shaohua Li
2010-04-20 15:01 ` Len Brown [this message]
2010-05-05  1:39   ` Shaohua Li
2010-05-06  6:33     ` Len Brown

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=alpine.LFD.2.00.1004201100220.2402@sony \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=shaohua.li@intel.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