From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 0/5] Missing interface declarations
Date: Thu, 14 Aug 2014 15:54:50 -0400 [thread overview]
Message-ID: <53ED140A.9060104@tresys.com> (raw)
In-Reply-To: <1407501202-14908-1-git-send-email-sven.vermeulen@siphos.be>
On 8/8/2014 8:33 AM, Sven Vermeulen wrote:
> It seems that a couple of interfaces in kernel/files.if are calling kernel_* interfaces that don't exist yet.
>
> Let's play safe and introduce them.
>
> Sven Vermeulen (5):
> Introduce kernel_delete_unlabeled_symlinks
> Introduce kernel_delete_unlabeled_pipes
> Introduce kernel_delete_unlabeled_sockets
> Introduce kernel_delete_unlabeled_blk_files
> Introduce kernel_delete_unlabeled_chr_files
>
> policy/modules/kernel/kernel.if | 90 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
I do several combinations of builds, so its strange that I didn't hit
these. The interfaces in the files module must not be used.
This set is merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2014-08-14 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 12:33 [refpolicy] [PATCH 0/5] Missing interface declarations Sven Vermeulen
2014-08-08 12:33 ` [refpolicy] [PATCH 1/5] Introduce kernel_delete_unlabeled_symlinks Sven Vermeulen
2014-08-08 12:33 ` [refpolicy] [PATCH 2/5] Introduce kernel_delete_unlabeled_pipes Sven Vermeulen
2014-08-08 12:33 ` [refpolicy] [PATCH 3/5] Introduce kernel_delete_unlabeled_sockets Sven Vermeulen
2014-08-08 12:33 ` [refpolicy] [PATCH 4/5] Introduce kernel_delete_unlabeled_blk_files Sven Vermeulen
2014-08-08 12:33 ` [refpolicy] [PATCH 5/5] Introduce kernel_delete_unlabeled_chr_files Sven Vermeulen
2014-08-14 19:54 ` Christopher J. PeBenito [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=53ED140A.9060104@tresys.com \
--to=cpebenito@tresys.com \
--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.