All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Stone <ahs3 at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] [RFC] proposed patch for some segfaults encountered
Date: Wed, 03 Jun 2015 15:26:47 -0600	[thread overview]
Message-ID: <556F7117.9050000@redhat.com> (raw)
In-Reply-To: 94F2FBAB4432B54E8AACC7DFDE6C92E37D2F1AB8@ORSMSX112.amr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

Awesome.  Thanks.

On 06/03/2015 03:06 PM, Moore, Robert wrote:
> Anyway, I added a check for a null target in AcpiDmIsValidTarget, and for the StoreOp target case. That should at least cover all of these types of cases.
> 
> 
>> -----Original Message-----
>> From: Devel [mailto:devel-bounces(a)acpica.org] On Behalf Of Al Stone
>> Sent: Monday, June 01, 2015 1:59 PM
>> To: devel(a)acpica.org
>> Subject: [Devel] [RFC] proposed patch for some segfaults encountered
>>
>> It's not clear to me that this is the correct way to handle a segfault
>> that was reported to me via Fedora.
>>
>> Using the ssdt9.dat file attached, a simple "iasl -d ssdt9.dat" will
>> segfault around calls to AcpiDmPromoteTarget -- and it turns out that the
>> Target pointer being passed into that function was sometimes null but not
>> being checked in the calling function, AcpiDmCheckForSymbolicOpcode.  So,
>> this patch adds in some checks for null pointers and can now get through
>> this particular problem.
>>
>> However, I did not study AcpiDmCheckForSymbolicOpcode long enough to
>> determine if the Target pointer in that function should or should not ever
>> be null.  So, this patch fixes this issue, but it may not be the proper
>> long term solution.
>>
>> --
>> ciao,
>> al
>> -----------------------------------
>> Al Stone
>> Software Engineer
>> Red Hat, Inc.
>> ahs3(a)redhat.com
>> -----------------------------------


-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------

             reply	other threads:[~2015-06-03 21:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 21:26 Al Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-03 21:06 [Devel] [RFC] proposed patch for some segfaults encountered Moore, Robert
2015-06-03 20:36 Moore, Robert
2015-06-03 19:54 Al Stone
2015-06-03 14:57 Moore, Robert
2015-06-03  0:37 Zheng, Lv
2015-06-02 20:13 Al Stone
2015-06-02 20:05 Moore, Robert
2015-06-02 19:06 Moore, Robert
2015-06-02 18:55 Moore, Robert
2015-06-02 16:47 Al Stone
2015-06-02 16:26 Moore, Robert
2015-06-02 15:07 Al Stone
2015-06-01 21:58 Moore, Robert
2015-06-01 20:59 Al Stone

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=556F7117.9050000@redhat.com \
    --to=devel@acpica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.