All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dean Nelson <dnelson at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] [PATCH] eliminate use after free in AcpiOsGetNextFilename()
Date: Tue, 19 Nov 2013 12:06:08 -0600	[thread overview]
Message-ID: <528BA890.5060503@redhat.com> (raw)
In-Reply-To: 94F2FBAB4432B54E8AACC7DFDE6C92E37C7A349E@ORSMSX103.amr.corp.intel.com

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

On 11/19/2013 10:54 AM, Moore, Robert wrote:
> Could you open a bugzilla on this? Thanks.
>
> https://bugs.acpica.org/

Just did.

Sorry, if I'm not doing things in the manner desired. I'm quite a
novice to acpica. If you prefer that we open BZs and not post patches
to the mailing list, I'm fine with that. Just let me know the protocol
to follow.

I'm pulling acpica-unix2 into RHEL and Coverity Scan (a static analysis
tool for C source code) flagged 164 potential 'defects'. A number are
false-positives, but some are legit. (I've not been through them all,
so I don't know the numbers.)

This was one of the legit ones, though the likelihood of it ever
showing up is about NIL. I posted the patch because it was trivial
and from it I hoped to learn how your process works.

As time allows, I hope to deal with the other legitimately flagged
'defects'. But it will probably be awhile, as there are other pressing
needs to attend to.

Thanks,
Dean

             reply	other threads:[~2013-11-19 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 18:06 Dean Nelson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-19 16:54 [Devel] [PATCH] eliminate use after free in AcpiOsGetNextFilename() Moore, Robert
2013-11-19 16:41 Dean Nelson

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=528BA890.5060503@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.