From: Greg KH <gregkh@linuxfoundation.org>
To: Erik Schmauss <erik.schmauss@intel.com>
Cc: linux-acpi@vger.kernel.org, rjw@rjwysocki.net, stable@vger.kernel.org
Subject: Re: [PATCH] ACPICA: AML Parser: fix parse loop to correctly skip erroneous extended opcodes
Date: Thu, 18 Oct 2018 07:06:04 +0200 [thread overview]
Message-ID: <20181018050604.GB25258@kroah.com> (raw)
In-Reply-To: <20181017212051.11171-1-erik.schmauss@intel.com>
On Wed, Oct 17, 2018 at 02:20:51PM -0700, Erik Schmauss wrote:
> AML opcodes come in two lengths: 1-byte opcodes and 2-byte, extended opcodes.
> If an error occurs due to illegal opcodes during table load, the AML parser
> needs to continue loading the table. In order to do this, it needs to skip
> parsing of the offending opcode and operands associated with that opcode.
>
> This change fixes the AML parse loop to correctly skip parsing of incorrect
> extended opcodes. Previously, only the short opcodes were skipped correctly.
>
> Signed-off-by: Erik Schmauss <erik.schmauss@intel.com>
> ---
> drivers/acpi/acpica/psloop.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2018-10-18 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 21:20 [PATCH] ACPICA: AML Parser: fix parse loop to correctly skip erroneous extended opcodes Erik Schmauss
2018-10-18 5:06 ` Greg KH [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=20181018050604.GB25258@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=erik.schmauss@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stable@vger.kernel.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