From: Johannes Segitz <jsegitz@suse.com>
To: Stephen Smalley <stephen.smalley@gmail.com>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: ebitmap: map size does not match my size on s390x
Date: Thu, 15 Jan 2015 14:02:28 +0100 [thread overview]
Message-ID: <20150115130228.GD24984@suse.de> (raw)
In-Reply-To: <CAB9W1A1bN6aBJi9-6RT+23BoH5dmppTv6WSUWtgVrJ21KOAqDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Wed, Jan 14, 2015 at 09:26:17AM -0500, Stephen Smalley wrote:
> There have been a couple of endianness fixes for
> /sys/fs/selinux/policy, e.g. see:
> 9085a6422 and b138004
Those commits solved the problem. Thank you.
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 --]
prev parent reply other threads:[~2015-01-15 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 11:03 ebitmap: map size does not match my size on s390x Johannes Segitz
2015-01-14 14:26 ` Stephen Smalley
2015-01-15 13:02 ` Johannes Segitz [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=20150115130228.GD24984@suse.de \
--to=jsegitz@suse.com \
--cc=selinux@tycho.nsa.gov \
--cc=stephen.smalley@gmail.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.