All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: selinux@tycho.nsa.gov
Subject: pcre compiled context files invalid with pcre updates?
Date: Wed, 9 Jul 2014 17:12:16 +0200	[thread overview]
Message-ID: <20140709151216.GA8142@siphos.be> (raw)

Hi all,

In Gentoo, we notice some unexpected behavior with the compiled
file_contexts files after upgrading (lib)pcre:

https://bugs.gentoo.org/show_bug.cgi?id=516608

I think what is happening is that the pcre data, which is built with one
pcre version, is not (fully) compatible with a more recent pcre version. In
the changelog of pcre I find type changes of (internal or not) variables by
pcre.

If this assumption is correct, perhaps we should store the pcre version used
to build the *.bin files in the file itself. Right now we store a magic (to
make sure it is a compiled file_contexts file) and a version specific for
libselinux, but not a version specific for PCRE.

The pcre header defines PCRE_MAJOR and PCRE_MINOR which we can use.

Do you think the above analysis makes sense? The bug linked earlier on has a
gdb backtrace for those interested. Any other pointers that might help us
troubleshoot this would be appreciated.

Wkr,
	Sven Vermeulen

             reply	other threads:[~2014-07-09 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 15:12 Sven Vermeulen [this message]
2014-07-09 15:27 ` pcre compiled context files invalid with pcre updates? Stephen Smalley
2014-07-09 15:36   ` Sven Vermeulen
2014-07-09 17:05     ` Stephen Smalley
2014-07-09 17:23       ` Sven Vermeulen

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=20140709151216.GA8142@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --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.