From: Stephen Smalley <sds@tycho.nsa.gov>
To: Sven Vermeulen <sven.vermeulen@siphos.be>,
Steve Lawrence <slawrence@tresys.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: SELinux Userspace Release: 20140826-rc1
Date: Fri, 29 Aug 2014 10:18:50 -0400 [thread overview]
Message-ID: <54008BCA.8070609@tycho.nsa.gov> (raw)
In-Reply-To: <54008AC4.6080600@tycho.nsa.gov>
On 08/29/2014 10:14 AM, Stephen Smalley wrote:
> On 08/29/2014 10:00 AM, Sven Vermeulen wrote:
>> On Fri, Aug 29, 2014 at 2:56 PM, Steve Lawrence <slawrence@tresys.com> wrote:
>>>>>>> Segmentation fault
>>>>> [...]
>>>>>> Can you provide a copy of your original policy prior to conversion?
>>>>>
>>>>> If you mean the policy.29 file, certainly. You can wget it from
>>>>> http://dev.gentoo.org/~swift/tmp/20140828-policy.29
>>>>
>>>> No, the contents of /etc/selinux/mcs. The migration script converts the
>>>> old policy module store, not the final kernel policy file.
>>>>
>>>
>>> Hmm, I'm unable to reproduce this. I think the policy store that Stephen
>>> mentions will be help to reproduce it.
>>>
>>
>> Certainly.
>>
>> The policy store can be found at
>> http://dev.gentoo.org/~swift/tmp/20140829-etc-selinux-mcs.tar.gz
>
> Hmm...semanage_migrate_store worked for me on that policy store.
>
> Can you reproduce the fault? If so, can you get debug info?
> Build with debug flags and run semanage_migrate_store under valgrind,
> perhaps?
Ok, I got it to fault (had to change my /etc/selinux/config
SELINUXTYPE=mcs to make it the active policy).
==18786== Invalid write of size 8
==18786== at 0xD83EC95: cil_reset_level (cil_reset_ast.c:214)
==18786== by 0xD83E9FE: cil_reset_user (cil_reset_ast.c:102)
==18786== by 0xD83F243: __cil_reset_node (cil_reset_ast.c:345)
==18786== by 0xD847FA0: cil_tree_walk_core (cil_tree.c:172)
==18786== by 0xD848109: cil_tree_walk (cil_tree.c:216)
==18786== by 0xD83F52C: cil_reset_ast (cil_reset_ast.c:471)
==18786== by 0xD84644A: cil_resolve_ast (cil_resolve_ast.c:3493)
==18786== by 0xD8179B6: cil_compile (cil.c:338)
==18786== by 0xE14E212: semanage_direct_commit (direct_api.c:1107)
==18786== by 0xE15C205: semanage_commit (handle.c:426)
==18786== by 0xDEF7264: _wrap_semanage_commit (semanageswig_wrap.c:4098)
==18786== by 0x31E68E0BD3: PyEval_EvalFrameEx (in
/usr/lib64/libpython2.7.so.1.0)
==18786== Address 0x20 is not stack'd, malloc'd or (recently) free'd
next prev parent reply other threads:[~2014-08-29 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 15:31 SELinux Userspace Release: 20140826-rc1 Steve Lawrence
2014-08-27 15:06 ` Sven Vermeulen
2014-08-27 16:10 ` Steve Lawrence
2014-08-28 19:58 ` Sven Vermeulen
2014-08-28 20:15 ` Stephen Smalley
2014-08-28 20:52 ` Sven Vermeulen
2014-08-29 12:11 ` Stephen Smalley
2014-08-29 12:56 ` Steve Lawrence
2014-08-29 14:00 ` Sven Vermeulen
2014-08-29 14:14 ` Stephen Smalley
2014-08-29 14:18 ` Stephen Smalley [this message]
2014-08-29 14:22 ` Steve Lawrence
2014-09-14 9:31 ` Sven Vermeulen
2014-09-15 12:12 ` Steve Lawrence
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=54008BCA.8070609@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.com \
--cc=sven.vermeulen@siphos.be \
/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.