From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: audit 1.2.7 released
Date: Wed, 20 Sep 2006 15:19:47 -0400 [thread overview]
Message-ID: <200609201519.47804.sgrubb@redhat.com> (raw)
In-Reply-To: <1158779559.15340.145.camel@moss-spartans.epoch.ncsc.mil>
On Wednesday 20 September 2006 15:12, Stephen Smalley wrote:
> SELinux userland code isn't supposed to assume any fixed max.
> libselinux does use an initial buffer size as a starting point when
> calling e.g. getxattr, but will resize the buffer to a larger size if
> necessary.
I try very hard to not have any memory allocations in the audit system to
prevent and possible failure due to fragmentation or leaks. I need to cap the
buffer size at something to meet this design goal.
-Steve
next prev parent reply other threads:[~2006-09-20 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 0:13 audit 1.2.7 released Steve Grubb
2006-09-19 21:05 ` Amy Griffis
2006-09-19 22:18 ` Steve Grubb
2006-09-20 19:12 ` Stephen Smalley
2006-09-20 19:19 ` Steve Grubb [this message]
2006-09-20 19:26 ` Paul Moore
2006-09-20 19:40 ` Steve Grubb
2006-09-21 19:43 ` Karl MacMillan
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=200609201519.47804.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox