public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Life is hard, and then you die" <ronald@innovation.ch>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Zheng, Lv" <lv.zheng@intel.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Moore, Robert" <robert.moore@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: ACPICA regression for empty ResourceTemplates
Date: Tue, 27 Jun 2017 11:59:17 -0700	[thread overview]
Message-ID: <20170627185917.GA14927@innovation.ch> (raw)
In-Reply-To: <20170627092425.GB5776@wunner.de>


On Tue, Jun 27, 2017 at 11:24:25AM +0200, Lukas Wunner wrote:
> On Tue, Jun 27, 2017 at 01:19:31AM +0000, Zheng, Lv wrote:
> > > On Mon, Jun 26, 2017 at 01:49:03PM +0200, Rafael J. Wysocki wrote:
> > > > On Mon, Jun 26, 2017 at 10:38 AM, Lukas Wunner <lukas@wunner.de> wrote:
> > > > > Hi Robert,
> > > > >
> > > > > ACPICA commit c8eac101 (= Linux commit a83019eb9f1f, "ACPICA: Update
> > > > > resource descriptor handling") is causing a regression when parsing
> > > > > an empty ResourceTemplate:
> > 
> > Can it be fixed by using this logic:
> > if (AmlLength < sizeof (AML_RESOURCE_END_TAG) && AmlLength)
> > Instead of the logic introduced in commit a83019eb9f1f?
> > if (AmlLength < sizeof (AML_RESOURCE_END_TAG))
> 
> Unfortunately not, AmlLength is not 0 but 2 in this case
> (= sizeof(struct aml_resource_end_tag)).

Actually, that will work here (the use of '<' ensures that). But it's
unclear whether this is semantically the correct thing, in particular
because a83019eb9f1f widened the cases where NO_RESOURCE_END_TAG is
returned, but the above suggestion narrows them. Unfortunately commit
a83019eb9f1f is quite vague about why it reverted back to '<='.


  Cheers,

  Ronald


  parent reply	other threads:[~2017-06-27 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26  8:38 ACPICA regression for empty ResourceTemplates Lukas Wunner
2017-06-26 11:49 ` Rafael J. Wysocki
2017-06-26 12:38   ` Lukas Wunner
2017-06-26 22:36     ` Rafael J. Wysocki
2017-06-27  1:19     ` Zheng, Lv
2017-06-27  9:24       ` Lukas Wunner
2017-06-27 15:08         ` Moore, Robert
2017-06-27 15:31           ` Rafael J. Wysocki
2017-06-28  8:59             ` Lukas Wunner
2017-06-27 18:59         ` Life is hard, and then you die [this message]
2017-06-27 19:23           ` Moore, Robert

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=20170627185917.GA14927@innovation.ch \
    --to=ronald@innovation.ch \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=lv.zheng@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=robert.moore@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