From: aranea@aixah.de (aranea at aixah.de)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] RFC: kernel_t exec rights on cgroup_t files
Date: Tue, 12 Feb 2013 22:51:11 +0100 [thread overview]
Message-ID: <20130212225111.3ee8e60d@gentp.lnet> (raw)
In-Reply-To: <20130212223207.38c2af27@gentp.lnet>
On Tue, 12 Feb 2013 22:32:07 +0100
<aranea@aixah.de> wrote:
> Here's another interesting thing: The file in question
> (/sys/fs/cgroup/openrc/notify_on_release) does not even exist!
> In fact, this directory doesn't include any files (but some
> directories) when booting in enforcing mode.
>
> In permissive mode however, there are some files
> (cgroup.clone_children, cgroup.event_control, cgroup.procs,
> notify_on_release, release_agent, tasks) there.
>
> This could mean that the error messages at 7 secs are only reactions
> to something which happens even earlier, when there's really no
> logging taking place.
Sorry, looks like I had one of these attacks of extreme dumbness you
sometimes have when the uptime is > 10h. Clearly these files don't
exist, as that's exactly what the error messages are complaining
about: It was for some reason not possible to create them.
I'll continue to debug this tommorow.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20130212/d30ff030/attachment-0001.bin
next prev parent reply other threads:[~2013-02-12 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 20:31 [refpolicy] RFC: kernel_t exec rights on cgroup_t files aranea at aixah.de
2013-02-12 20:34 ` Dominick Grift
2013-02-12 20:47 ` aranea at aixah.de
2013-02-12 21:12 ` Dominick Grift
2013-02-12 21:25 ` aranea at aixah.de
2013-02-12 21:32 ` aranea at aixah.de
2013-02-12 21:51 ` aranea at aixah.de [this message]
2013-02-15 21:12 ` Luis Ressel
-- strict thread matches above, loose matches on Subject: below --
2013-02-12 19:47 Sven Vermeulen
2013-02-12 20:00 ` Dominick Grift
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=20130212225111.3ee8e60d@gentp.lnet \
--to=aranea@aixah.de \
--cc=refpolicy@oss.tresys.com \
/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.