[Bug 5831] New: execmod from SeLinux interfering with program execution?

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=5831

Summary: execmod from SeLinux interfering with program execution?
           Product: Wine
           Version: CVS
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: wine-misc
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I try to run the latest cvs, with SeLinux enabled, and i get in my log with 
this kind of mesages:

audit(1154453141.552:774): avc:  denied  { execmod } for  pid=17382 
comm="hu.exe" name="msacm32.drv.so" dev=hda2 ino=2380103 
scontext=root:system_r:unconfined_t:s0-s0:c0.c255 
tcontext=root:object_r:src_t:s0 tclass=file
audit(1154453141.559:775): avc:  denied  { execmod } for  pid=17382 
comm="hu.exe" name="midimap.dll.so" dev=hda2 ino=2379962 
scontext=root:system_r:unconfined_t:s0-s0:c0.c255 
tcontext=root:object_r:src_t:s0 tclass=file
audit(1154453141.595:776): avc:  denied  { execmod } for  pid=17382 
comm="hu.exe" name="psapi.dll.so" dev=hda2 ino=1368201 
scontext=root:system_r:unconfined_t:s0-s0:c0.c255 
tcontext=root:object_r:src_t:s0 tclass=file
audit(1154453141.596:777): avc:  denied  { execmod } for  pid=17382 
comm="hu.exe" name="dbghelp.dll.so" dev=hda2 ino=2286081 
scontext=root:system_r:unconfined_t:s0-s0:c0.c255 
tcontext=root:object_r:src_t:s0 tclass=file

I ran it as root to be sure i don't get any troubles(no luck), this also 
happens as a normal user.

A early wine 0.9.17 (fedora extras wine 0.9.17-1) manages to run the program 
just fine, but more recent wine's require:
setsebool -P allow_execmod=1     
to work properly.

Also, i did a little research, and i found this: 
http://www.winehq.org/pipermail/wine-patches/2005-June/018398.html
But the thing is, i didn't get any error messages in the console, no err, the 
loading of the program just stopped, but i could still see the executable and 
wineserver in the process table still using cpu. 
Soooo, is this a wine bug, a program flaw, or a SeLinux screw-up ?