> >Looks like the same problem your having, have you seen this? > >http://www.nsa.gov/selinux/list-archive/0606/thread_body10.cfm#15927 > > >-Max Hm. Yup, that's exactly what I'm seeing. And the bug report referenced in that post explains why ("SELinux sets up the inode security state upon d_instantiate, so it expects the inode mode to be set (so that it can set the inode security class). cifs appears to call d_instantiate before fully setting up the inode state."). Now I'm just wondering what I'm doing wrong because the report says this issue is fixed in kernels 2.6.18 and above, and I'm running a kernel > 2.6.18...... Thanks, Lucas -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
