From: Johannes Segitz <jsegitz@suse.com>
To: selinux@tycho.nsa.gov
Subject: ebitmap: map size does not match my size on s390x
Date: Wed, 14 Jan 2015 12:03:34 +0100 [thread overview]
Message-ID: <20150114110334.GA24984@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
Hello,
running sepolgen-ifgen fails on s390x. It fails because calling
# sepolgen-ifgen-attr-helper /sys/fs/selinux/policy /tmp/tmpsSrJj3
gives:
libsepol.policydb_index_others: security: 7 users, 47 roles, 3156 types, 201 bools
libsepol.policydb_index_others: security: 1 sens, 1024 cats
libsepol.policydb_index_others: security: 83 classes, 59401 rules, 9799 cond rules
security: ebitmap: map size 1400 does not match my size 64 (high bit was 1545)
error(s) encountered while parsing configuration
I use version 2.3 of the userspace tools on SLE 12 with kernel 3.12.28. The
policy is based on Fedoras policy with some extension for SUSE
(f85b52d1c6805e9b0a8bd2a4a4332e66e4b52c00 for the base policy and
627644e1bb9c6f851c2466ab6e0eec7607f472cd for contrib). This combination
works fine on other architectures, only s390x shows this behavior. I did
not work on s390x before so I don't know if this ever worked.
The message comes from libsepol/src/ebitmap.c:361. Could this be a
endianness issue?
Best regards
Johannes
--
Johannes Segitz SUSE Security Team
GPG Key E7C81FA0 EE16 6BCE AD56 E034 BFB3 3ADD 7BF7 29D5 E7C8 1FA0
SUSE LINUX GmbH Maxfeldstraße 5 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-01-14 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 11:03 Johannes Segitz [this message]
2015-01-14 14:26 ` ebitmap: map size does not match my size on s390x Stephen Smalley
2015-01-15 13:02 ` Johannes Segitz
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=20150114110334.GA24984@suse.de \
--to=jsegitz@suse.com \
--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.