Bug 331041

Summary: [PATCH] libvirt -> dnsmasq AVC causes failure
Product: [Fedora] Fedora Reporter: Warren Togami <wtogami>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: veillard
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-15 13:17:00 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235704    

Description Warren Togami 2007-10-13 20:19:51 EDT
[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-13 20:41:01 EDT
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 13:15:17 EDT
You can search through the active policy with sesearch

sesearch --allow | grep dnmasq | grep virt_var_lib
Comment 3 Daniel Walsh 2007-10-15 13:17:00 EDT
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.