From: Joshua Brindle <method@manicmethod.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Eric Paris <eparis@redhat.com>, selinux <selinux@tycho.nsa.gov>
Subject: Re: segfault in semodule
Date: Fri, 22 Feb 2008 12:56:38 -0500 [thread overview]
Message-ID: <47BF0CD6.6000802@manicmethod.com> (raw)
In-Reply-To: <1203702113.2804.71.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Fri, 2008-02-22 at 11:55 -0500, Joshua Brindle wrote:
>
>> Eric Paris wrote:
>>
>>> I added "allow-unknown = deny" in semanage.conf and ran semodule -R
>>>
>>> [root@dhcp231-146 ~]# semodule -R
>>> error parsing semanage configuration file: syntax error
>>> semodule: Could not create semanage handle
>>> semodule: handle.c:123: semanage_is_connected: Assertion `sh != ((void *)0)' failed.
>>> Segmentation fault
>>>
>>> It was supposed to bail (allow-unknown is not a valid entry, it should
>>> be handle-unknown) but it wasn't supposed to segfault. Maybe someone
>>> who knows this code can find/fix it really quickly, if not I'm sure I'll
>>> get to look at it when it gets to the top of my list in 10 or 12
>>> months :)
>>>
>>> policycoreutils-2.0.43-2.fc9.x86_64
>>>
>>>
>> This is totally untested but should fix it:
>>
>
> I suppose the other option would be to make semanage_is_connected()
> return 0 if sh == NULL rather than assert'ing that sh is non-NULL.
> Then the same error path could be used.
>
>
I suppose, I think the basic philosophy in this library was that passing
a null handle to any function that requires a handle is a bug and should
be fixed. I'd hate to fix it in semanage_is_connected() and leave the
asserts every where else.
>> Index: trunk/policycoreutils/semodule/semodule.c
>> ===================================================================
>> --- trunk/policycoreutils/semodule/semodule.c (revision 2808)
>> +++ trunk/policycoreutils/semodule/semodule.c (working copy)
>> @@ -285,7 +285,7 @@
>> if (!sh) {
>> fprintf(stderr, "%s: Could not create semanage handle\n",
>> argv[0]);
>> - goto cleanup;
>> + goto cleanup_nohandle;
>> }
>>
>> if (store) {
>> @@ -473,6 +473,8 @@
>> }
>> }
>> semanage_handle_destroy(sh);
>> +
>> + cleanup_nohandle:
>> cleanup();
>> exit(status);
>> }
>>
>>
>>
>> --
>> This message was distributed to subscribers of the selinux mailing list.
>> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
>> the words "unsubscribe selinux" without quotes as the message.
>>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2008-02-22 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 16:11 segfault in semodule Eric Paris
2008-02-22 16:55 ` Joshua Brindle
2008-02-22 17:22 ` Stephen Smalley
2008-02-22 17:41 ` Stephen Smalley
2008-02-22 17:56 ` Joshua Brindle [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=47BF0CD6.6000802@manicmethod.com \
--to=method@manicmethod.com \
--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.