Linux ACPI
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Jeremy Compostella <jeremy.compostella@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jeremy Compostella <jeremy.compostella@gmail.com>,
	"Gross, Mark" <mark.gross@intel.com>
Subject: Re: [PATCH] acpi: Incorrect ACPI tables walk in acpi_tables_sysfs_init
Date: Thu, 21 Nov 2013 14:27:22 +0100	[thread overview]
Message-ID: <10117757.kh27mk2tn6@vostro.rjw.lan> (raw)
In-Reply-To: <87bo1e839w.fsf@tldlab276.tl.intel.com>

On Thursday, November 21, 2013 11:20:27 AM Jeremy Compostella wrote:
> Date: Thu, 21 Nov 2013 11:20:23 +0100
> Message-ID: <87d2lu83a0.fsf@tldlab276.tl.intel.com>
> MIME-Version: 1.0
> Content-Type: text/plain
> --text follows this line--
> Hi,
> 
> When executing on a ACPI Hardware reduced hardware, all the ACPI tables are not
> exposed in sysfs due to the fact that FACS is silently ignored by the kernel in
> ACPI hardware reduced and, moreover, the acpi_tables_sysfs_init ACPI table walk
> is buggy and stop too soon.
> 
> The acpi_tables_sysfs_init function should to rely on the appropriate
> acpi_status return values to decide or not to stop the iteration.  This way,
> when running on a ACPI Reduced Harware environment where the FACS table is
> silently ignored by the kernel or some ACPI table are not correctly memory
> mapped or have a bad checksum it would not stop the iteration.
> 
> Signed-off-by: Jeremy Compostella <jeremy.compostella@intel.com>

Since this is a fix, I've modified the subject and changelog slightly and
queued up the patch for the next ACPI pull request (next week).

Thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-11-21 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 10:20 [PATCH] acpi: Incorrect ACPI tables walk in acpi_tables_sysfs_init Jeremy Compostella
2013-11-21 13:27 ` Rafael J. Wysocki [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=10117757.kh27mk2tn6@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=jeremy.compostella@gmail.com \
    --cc=jeremy.compostella@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.gross@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