From: Lucas Emery <lucas@rowdy.com>
To: selinux@tycho.nsa.gov
Subject: Re: selinux freaking out about samba share
Date: Wed, 6 Aug 2008 16:39:49 -0400 (EDT) [thread overview]
Message-ID: <7478930.41218055185078.JavaMail.SYSTEM@Spacetime> (raw)
In-Reply-To: <11565128.21218055038859.JavaMail.SYSTEM@Spacetime>
>
>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@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
parent reply other threads:[~2008-08-06 20:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <11565128.21218055038859.JavaMail.SYSTEM@Spacetime>]
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=7478930.41218055185078.JavaMail.SYSTEM@Spacetime \
--to=lucas@rowdy.com \
--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.