Bug 331041 - [PATCH] libvirt -> dnsmasq AVC causes failure
Summary: [PATCH] libvirt -> dnsmasq AVC causes failure
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F8Target
TreeView+ depends on / blocked
 
Reported: 2007-10-14 00:19 UTC by Warren Togami
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-15 17:17:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Warren Togami 2007-10-14 00:19:51 UTC
[root@newcaprica dnsmasq]# service libvirtd restart
Stopping libvirtd daemon:                                  [  OK  ]
Starting libvirtd daemon:                                  [  OK  ]
dnsmasq[24840]: segfault at 00000000ffffffff rip 00000037dfa79530 rsp
00007fff5d62f4d8 error 4

module dnsmasqrule 1.0;

require {
        type virt_var_lib_t;
        type dnsmasq_t;
        class dir { write add_name };
        class file create;
}

#============= dnsmasq_t ==============
allow dnsmasq_t virt_var_lib_t:dir { write add_name };
allow dnsmasq_t virt_var_lib_t:file create;

Comment 1 Warren Togami 2007-10-14 00:41:01 UTC
I am seriously confused.  Prior to semodule -i, it failed on every attempt.  But
now after semodule -r and even a reboot, it wont fail anymore.

How can I be sure that my custom semodules are truly being removed?  This isn't
the first time this has happened to me.


Comment 2 Daniel Walsh 2007-10-15 17:15:17 UTC
You can search through the active policy with sesearch

sesearch --allow | grep dnmasq | grep virt_var_lib


Comment 3 Daniel Walsh 2007-10-15 17:17:00 UTC
BTW an update to policy includes these rules in dnmasq


optional_policy(`
	virt_rw_lib_files(dnsmasq_t)
')

So if inbetween the time you installed your policy module.  I fix upstream and
you update, this could happen.



Note You need to log in before you can comment on or make changes to this bug.