From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH] Don't free() static data in libauparse
Date: Mon, 2 Jun 2008 11:42:28 -0400 [thread overview]
Message-ID: <200806021142.29018.sgrubb@redhat.com> (raw)
In-Reply-To: <1212416953.2746.17.camel@amilo>
On Monday 02 June 2008 10:29:13 Miloslav Trmač wrote:
> The "interpretation" code in libuparse stores literal strings as
> interpreted data for the second operand of fcntl(). This causes a crash
> in free() when freeing the record.
Applied. Thanks!
-Steve
prev parent reply other threads:[~2008-06-02 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 14:29 [PATCH] Don't free() static data in libauparse Miloslav Trmač
2008-06-02 15:42 ` Steve Grubb [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=200806021142.29018.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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 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.