From: Stephen Smalley <sds@tycho.nsa.gov>
To: Richard Yao <ryao@gentoo.org>,
mthode@mthode.org, Brian Behlendorf <behlendorf1@llnl.gov>
Cc: behlendorf@llnl.gov, selinux@tycho.nsa.gov
Subject: Re: file access causes a kernel bug
Date: Thu, 30 Jan 2014 13:10:59 -0500 [thread overview]
Message-ID: <52EA95B3.506@tycho.nsa.gov> (raw)
In-Reply-To: <52EA8B84.5010006@gentoo.org>
On 01/30/2014 12:27 PM, Richard Yao wrote:
> On 01/30/2014 12:07 PM, Matthew Thode wrote:
>> On 01/30/2014 10:41 AM, Stephen Smalley wrote:
>>> On 01/30/2014 10:51 AM, Matthew Thode wrote:
>>>> On 01/30/2014 09:45 AM, Stephen Smalley wrote:
>>>>> We'll have to investigate, as that obviously shouldn't be possible.
>>>>> Wouldn't be allowed in enforcing mode or for any non-root process.
>
> This is an untested conjecture, but I believe that a FUSE filesystem
> could be used to trigger this in enforcing mode. If I am right, a custom
> FUSE filesystem could trigger it with ease. However, I do not see what
> that would accomplish beyond triggering the BUG_ON.
SELinux does not presently request or use xattrs from FUSE filesystems,
so I don't believe this is presently an issue, but I understand.
>
>>> Try the attached patch.
>>>
>>>
>> Confirmed that this fixes it :D thanks a ton for this.
>
> This patch looks good to me. Feel free to append my Acked-by:
>
> Acked-by: Richard Yao <ryao@gentoo.org>
>
prev parent reply other threads:[~2014-01-30 18:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 8:04 file access causes a kernel bug Matthew Thode
2014-01-29 8:11 ` Matthew Thode
2014-01-29 13:55 ` Paul Moore
2014-01-29 14:07 ` Stephen Smalley
2014-01-29 14:17 ` Stephen Smalley
2014-01-29 16:58 ` Matthew Thode
2014-01-29 21:36 ` Stephen Smalley
2014-01-29 22:35 ` Brian Behlendorf
2014-01-29 22:39 ` Richard Yao
2014-01-30 8:20 ` Matthew Thode
2014-01-30 13:43 ` Stephen Smalley
2014-01-30 15:38 ` Matthew Thode
2014-01-30 15:45 ` Stephen Smalley
2014-01-30 15:51 ` Matthew Thode
2014-01-30 16:41 ` Stephen Smalley
2014-01-30 17:07 ` Matthew Thode
2014-01-30 17:19 ` Paul Moore
2014-01-30 17:35 ` Matthew Thode
2014-01-30 19:19 ` Paul Moore
2014-02-04 3:41 ` Per Nystrom
2014-02-05 17:15 ` Matthew Thode
2014-02-05 17:18 ` Paul Moore
2014-01-30 17:27 ` Richard Yao
2014-01-30 18:10 ` Stephen Smalley [this message]
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=52EA95B3.506@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=behlendorf1@llnl.gov \
--cc=behlendorf@llnl.gov \
--cc=mthode@mthode.org \
--cc=ryao@gentoo.org \
--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.