public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Len Brown <lenb@kernel.org>
Cc: sfi-devel@simplefirmware.org, linux-kernel@vger.kernel.org,
	Feng Tang <feng.tang@intel.com>, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 6/8] SFI: add ACPI extensions
Date: Tue, 23 Jun 2009 14:18:42 +0200	[thread overview]
Message-ID: <87my7z16u5.fsf@basil.nowhere.org> (raw)
In-Reply-To: <505434cf34f7438a65262060df88b0638511684d.1245740912.git.len.brown@intel.com> (Len Brown's message of "Tue, 23 Jun 2009 03:14:04 -0400")

Len Brown <lenb@kernel.org> writes:
>
> diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c
> index 646d39c..921746f 100644
> --- a/drivers/acpi/tables.c
> +++ b/drivers/acpi/tables.c
> @@ -277,6 +277,9 @@ int __init acpi_table_parse(char *id, acpi_table_handler handler)
>  	struct acpi_table_header *table = NULL;
>  	acpi_size tbl_size;
>  
> +	if (acpi_disabled)
> +		return 1;
> +

This seems like a weird place to hook this in. Shouldn't that be somewhere else, more
high level?


> +#include <linux/acpi.h>
> +#include <linux/kernel.h>
> +#include <linux/sfi.h>
> +#include "sfi_core.h"
> +
> +#undef PREFIX

Nobody should set PREFIX in headers? If they do better fix the headers.


> + * sfi_acpi_parse_xsdt()
> + *
> + * Parse the ACPI XSDT for later access by sfi_acpi_table_parse().
> + */
> +static int __init sfi_acpi_parse_xsdt(struct sfi_table_header *table)
> +{
> +	int num_entries, i;
> +
> +	struct acpi_table_xsdt *xsdt = (struct acpi_table_xsdt *) table;
> +
> +	BUG_ON(!xsdt);


Seems like a pointless BUG_ON, the NULL pointer reference next to it is
obvious enough.

> +
> +	num_entries = (xsdt->header.length - sizeof(struct acpi_table_header) /
> +		sizeof(u64));
> +
> +	pr_debug(PREFIX "XSDT has %d entries\n", num_entries);
> +
> +	for (i = 0; i < num_entries; i++)
> +		sfi_tb_install_table(xsdt->table_offset_entry[i], SFI_ACPI_TABLE);

Shouldn't this have some more sanity checking, e.g. for overflows?


-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2009-06-23 12:19 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  7:13 [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial support Len Brown
2009-06-23  7:13 ` [PATCH 1/8] SFI: Simple Firmware Interface - new Linux sub-system Len Brown
2009-06-23  7:14   ` [PATCH 2/8] SFI: include/linux/sfi.h Len Brown
2009-06-23  7:28     ` Ingo Molnar
2009-06-23  7:47       ` Feng Tang
2009-06-23  8:00         ` Ingo Molnar
2009-06-23  8:02           ` Feng Tang
2009-06-23  8:09             ` Ingo Molnar
2009-06-23 15:14               ` H. Peter Anvin
2009-06-30 21:57       ` Andrew Morton
2009-06-30 21:59         ` Ingo Molnar
2009-06-23  9:06     ` Sam Ravnborg
2009-06-23 15:52       ` Feng Tang
2009-06-23 19:26         ` Sam Ravnborg
2009-06-23  7:14   ` [PATCH 3/8] SFI: core support Len Brown
2009-06-23  7:56     ` Ingo Molnar
2009-06-23  8:32       ` Feng Tang
2009-06-23  9:03         ` Ingo Molnar
2009-06-23  9:15           ` Feng Tang
2009-06-23 17:20       ` Len Brown
2009-06-23 19:20         ` Ingo Molnar
2009-06-23 12:32     ` Andi Kleen
2009-06-23 16:57       ` Len Brown
2009-06-24  3:34       ` Feng Tang
2009-06-24  7:12         ` Andi Kleen
2009-06-24  7:40           ` Feng Tang
2009-06-24  7:55             ` Andi Kleen
2009-06-23  7:14   ` [PATCH 4/8] SFI: Hook boot-time initialization Len Brown
2009-06-23  7:14   ` [PATCH 5/8] SFI: Hook e820 memory map initialization Len Brown
2009-06-23  7:14   ` [PATCH 6/8] SFI: add ACPI extensions Len Brown
2009-06-23 12:18     ` Andi Kleen [this message]
2009-06-23 16:51       ` Len Brown
2009-06-23  7:14   ` [PATCH 7/8] SFI, PCI: Hook MMCONFIG Len Brown
2009-06-23  7:14   ` [PATCH 8/8] SFI: expose IO-APIC routines to SFI, not just ACPI Len Brown
2009-06-23  7:58     ` Ingo Molnar
2009-06-23  7:23   ` [PATCH 1/8] SFI: Simple Firmware Interface - new Linux sub-system Ingo Molnar
2009-06-23 18:31 ` [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial support Matthew Garrett
2009-06-23 18:41   ` Len Brown
2009-06-22 19:43     ` Pavel Machek
2009-06-24 21:13       ` Len Brown
2009-07-11 22:02         ` Pavel Machek
2009-07-13  3:25           ` [SFI-devel] " Peter Stuge
2009-06-23 18:51     ` Matthew Garrett
2009-06-23 20:00       ` Len Brown
2009-06-23 20:23         ` Matthew Garrett
2009-06-23 20:45           ` Matthew Garrett
2009-06-23 21:23             ` Alan Cox
2009-06-23 22:34               ` Len Brown
2009-06-23 22:20             ` Len Brown
2009-06-23 22:56               ` Matthew Garrett
2009-06-23 23:00               ` [SFI-devel] " Justen, Jordan L
2009-06-24  0:35                 ` Len Brown
2009-06-23 21: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=87my7z16u5.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=feng.tang@intel.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfi-devel@simplefirmware.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