From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Performance of libauparse
Date: Wed, 1 Oct 2008 14:46:26 -0400 [thread overview]
Message-ID: <200810011446.26752.sgrubb@redhat.com> (raw)
In-Reply-To: <48E3A08C.2030501@redhat.com>
On Wednesday 01 October 2008 12:08:44 Matthew Booth wrote:
> > Close, but not quite. I say we can't change the kernel without complete
> > backwards compatibility. Show me the right solution and we can get
> > there, we just can't throw away what's already there.
>
> My other mail listed 6 ways in which audit *has already broken*
> userspace through non-backwards compatibility.
Are they verified broken or just that something changed? Backwards
compatibility was worked in wherever possible.
>The situation is still very messy, and this will continue to happen because
>the protocol has evolved organically rather than through deliberate design,
>and was not designed for extensibility.
There was a deliberate design. Compactness and extensibility are sometimes at
odds, though. But this is straying way away from your original post about
performance improvements - which I would find to be topic worth talking
about. I will not participate in any rehash of past discussions about parsing
or representation of data.
-Steve
next prev parent reply other threads:[~2008-10-01 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 13:34 Performance of libauparse Matthew Booth
2008-09-30 18:34 ` Steve Grubb
2008-09-30 19:18 ` John Dennis
2008-09-30 22:18 ` Matthew Booth
2008-10-01 13:15 ` Eric Paris
2008-10-01 16:08 ` Matthew Booth
2008-10-01 18:46 ` Steve Grubb [this message]
2008-10-01 18:38 ` Paul Moore
2008-10-01 19:20 ` LC Bruzenak
2008-10-01 19:31 ` LC Bruzenak
2008-10-01 21:19 ` Paul Moore
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=200810011446.26752.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.