All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Emery <lucas@rowdy.com>
To: selinux@tycho.nsa.gov
Subject: selinux freaking out about cifs share
Date: Wed, 6 Aug 2008 14:49:49 -0400 (EDT)	[thread overview]
Message-ID: <20657148.261218048588328.JavaMail.SYSTEM@Spacetime> (raw)
In-Reply-To: <32753706.241218048327109.JavaMail.SYSTEM@Spacetime>

Someone on #selinux suggested I post this issue I'm having to the list, so here goes.

I've got pages and pages of the following error in /var/log/messages:

SELinux is preventing httpd (httpd_t) "0x100000" to 'somefile' (httpd_sys_content_t).

The files in question are on a remote cifs share.  SELinux context on all files is httpd_sys_content_t.

Output of sealert follows:

Summary:

SELinux is preventing httpd (httpd_t) "0x100000" to 'somefile'
(httpd_sys_content_t).

Additional Information:

Source Context                root:system_r:httpd_t
Target Context                system_u:object_r:httpd_sys_content_t
Target Objects                'blah' [ file ]
Source                        httpd
Source Path                   /usr/sbin/httpd
Port                          <Unknown>
Host                          localhost
Source RPM Packages           httpd-2.2.3-11.el5_1.centos.3
Target RPM Packages
Policy RPM                    selinux-policy-2.4.6-137.1.el5
Selinux Enabled               True
Policy Type                   targeted
MLS Enabled                   True
Enforcing Mode                Enforcing
Plugin Name                   catchall_file
Host Name                     localhost
Platform                      Linux localhost 2.6.18-92.1.6.el5 #1 SMP Wed
Jun 25
                             13:49:24 EDT 2008 i686 i686
Alert Count                   43
First Seen                    Mon Aug  4 11:10:09 2008
Last Seen                     Wed Aug  6 11:25:14 2008
Local ID                      4f544c6a-2eb9-4025-8bcf-f4c4383f26d2
Line Numbers

Raw Audit Messages

host=localhost type=AVC msg=audit(1218036314.997:95776): avc:  denied  {
0x100000 } for  pid=10564 comm="httpd" name="241" dev=cifs ino=7278187
scontext=root:system_r:httpd_t:s0
tcontext=system_u:object_r:httpd_sys_content_t:s0 tclass=file

host=localhost type=SYSCALL msg=audit(1218036314.997:95776): arch=40000003
syscall=195 success=no exit=-13 a0=9bc1a10 a1=bfa580bc a2=333ff4 a3=8170
items=0 ppid=10496 pid=10564 auid=0 uid=48 gid=48 euid=48 suid=48 fsuid=48
egid=48 sgid=48 fsgid=48 tty=(none) ses=511 comm="httpd"
exe="/usr/sbin/httpd" subj=root:system_r:httpd_t:s0 key=(null)

I'm running CIFS module version 1.50cRH

Red Hat thinks this is a kernel bug and I have filed a bug report with them.

I can temporarily fix the problem with a reboot, but that's  treating the symptom and not the cause, and this is a production box so random reboots are not really a workable solution.

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.

       reply	other threads:[~2008-08-06 18:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <32753706.241218048327109.JavaMail.SYSTEM@Spacetime>
2008-08-06 18:49 ` Lucas Emery [this message]
2008-08-06 19:42   ` selinux freaking out about cifs share Justin Mattock
2008-08-06 20:16   ` max

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=20657148.261218048588328.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.