From: Daniel J Walsh <dwalsh@redhat.com>
To: Lennart Poettering <lennart@poettering.net>
Cc: Colin Walters <walters@verbum.org>,
russell@coker.com.au, Eric Paris <eparis@redhat.com>,
selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: A filename to label translation daemon
Date: Mon, 13 Aug 2012 13:36:17 -0400 [thread overview]
Message-ID: <50293B11.9010105@redhat.com> (raw)
In-Reply-To: <20120810141747.GA909@tango.0pointer.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/10/2012 10:17 AM, Lennart Poettering wrote:
> On Fri, 10.08.12 16:11, Lennart Poettering (lennart@poettering.net) wrote:
>
>>> * Your mmap file is in some data format - you can make up your own,
>>> but I like using
>>> http://developer.gnome.org/glib/stable/glib-GVariant.html * Check the
>>> timestamp on the regexp text file versus the cached copy, if newer, use
>>> the text file * Otherwise, mmap the cached blob, loop through each
>>> regexp, passing a pointer to the mmap cache file for regexec()
>>
>> Well, the main bits are not actually stored in regex_t afaics. They are
>> stored in regex_t::buffer. But that makes this kind of caching really
>> difficult, because that is a pointer and storing a pointer in an mmap()
>> region makes no sense.
>>
>> Dunno, maybe another regex library is more suitable for this...
>
> PCRE appears to be perfectly suited for this. See pcreprecompile(3). They
> have an interface explicitly designed for this. And PCRE is used by
> numerous projects already, so should be safe to use for SELinux too?
>
> Lennart
>
This seems like the best solution? If upstream will accept it. We could
rebuild the regex data when semanage modifies the file context.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlApOxEACgkQrlYvE4MpobOtgwCdGLgwt60AY3L+pHuQzQnrREEW
eQ4AoIgVktEglFqzInQJSZpUQLfEFk9H
=YWaU
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2012-08-13 17:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 19:31 A filename to label translation daemon Eric Paris
2012-08-08 20:05 ` Stephen Smalley
2012-08-08 20:52 ` Daniel J Walsh
2012-08-08 20:55 ` Eric Paris
2012-08-08 21:26 ` Colin Walters
2012-08-09 14:37 ` Russell Coker
2012-08-09 17:06 ` Daniel J Walsh
2012-08-09 17:51 ` Colin Walters
[not found] ` <20120810141101.GC32076@tango.0pointer.de>
[not found] ` <20120810141747.GA909@tango.0pointer.de>
2012-08-13 17:36 ` Daniel J Walsh [this message]
2012-08-13 17:55 ` Colin Walters
2012-08-13 18:06 ` Daniel J Walsh
2012-08-14 11:18 ` Russell Coker
2012-08-14 12:38 ` Eric Paris
2012-08-14 14:01 ` Eric Paris
2012-08-14 16:48 ` Stephen Smalley
2012-08-14 17:21 ` Eric Paris
2012-08-14 22:34 ` Russell Coker
2012-08-15 5:56 ` Russell Coker
2012-08-15 13:22 ` Eric Paris
2012-08-16 23:51 ` Eric Paris
2012-08-10 2:28 ` Russell Coker
2012-08-10 12:39 ` Daniel J Walsh
2012-08-10 13:35 ` Russell Coker
2012-08-12 11:02 ` Daniel J Walsh
[not found] ` <20120810140503.GB32076@tango.0pointer.de>
2012-08-12 11:03 ` Daniel J Walsh
[not found] ` <20120813151821.GB4861@redhat.com>
2012-08-13 16:37 ` Daniel J Walsh
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=50293B11.9010105@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=lennart@poettering.net \
--cc=russell@coker.com.au \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=walters@verbum.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.