From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Eric Paris <eparis@redhat.com>, selinux@tycho.nsa.gov
Subject: Re: pcre compiled context files invalid with pcre updates?
Date: Wed, 9 Jul 2014 19:23:21 +0200 [thread overview]
Message-ID: <20140709172321.GA10669@siphos.be> (raw)
In-Reply-To: <53BD7645.8060407@tycho.nsa.gov>
On Wed, Jul 09, 2014 at 01:05:09PM -0400, Stephen Smalley wrote:
> >> The issue came up again in the context of cross-compiling in:
> >> http://marc.info/?t=139275881100002&r=1&w=2
> >> and there was a willingness to add a version but I don't think anyone
> >> proposed a patch to do so. But even with the version, using the PCRE
> >> version effectively just means that you'll need to regenerate on each
> >> new library version anyway, right? So what do we gain versus the
> >> current approach of regenerating on pcre updates?
> >
> > There's a small period between the pcre upgrade and the selinux-policy
> > update in which we'll get these failures again (and in Gentoo, the
> > installation of selinux-policy will fail because a relabeling operation on
> > the files would occur which will segfault - but that's something we need to
> > tackle in Gentoo).
>
> I see. How about the attached patch then?
The patch works fine, thanks. Tested with libselinux-2.3, and pcre 8.33 / 8.35. I
timed the difference of setfiles commands to "acknowledge" that the .bin
files were ignored when they needed to (longer duration means regular
context files are used instead of .bin files).
Wkr,
Sven Vermeulen
prev parent reply other threads:[~2014-07-09 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 15:12 pcre compiled context files invalid with pcre updates? Sven Vermeulen
2014-07-09 15:27 ` Stephen Smalley
2014-07-09 15:36 ` Sven Vermeulen
2014-07-09 17:05 ` Stephen Smalley
2014-07-09 17:23 ` Sven Vermeulen [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=20140709172321.GA10669@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=eparis@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.