From: Paul Moore <pmoore@redhat.com>
To: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: [PATCH 0/2] Fix some multiqueue TUN problems
Date: Mon, 14 Jan 2013 12:12:06 -0500 [thread overview]
Message-ID: <20130114170837.31874.78897.stgit@localhost> (raw)
No significant changes to this patchset since the last posting, just a
slight merge with the recent changes in tun_set_queue() and some
Acked-by and Tested-by additions. I believe all the concerns have been
addressed and this patch is ready for merging.
Dave, I think it makes the most sense for this to get pulled in via the
netdev tree but if you think otherwise let me know and I'll go bug
James and Eric.
-Paul
---
Paul Moore (2):
selinux: add the "attach_queue" permission to the "tun_socket" class
tun: fix LSM/SELinux labeling of tun/tap devices
drivers/net/tun.c | 23 +++++++++++---
include/linux/security.h | 59 +++++++++++++++++++++++++++--------
security/capability.c | 24 ++++++++++++--
security/security.c | 28 ++++++++++++++---
security/selinux/hooks.c | 50 +++++++++++++++++++++++-------
security/selinux/include/classmap.h | 2 +
security/selinux/include/objsec.h | 4 ++
7 files changed, 152 insertions(+), 38 deletions(-)
next reply other threads:[~2013-01-14 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 17:12 Paul Moore [this message]
2013-01-14 17:12 ` [PATCH 1/2] selinux: add the "attach_queue" permission to the "tun_socket" class Paul Moore
2013-01-14 17:12 ` [PATCH 2/2] tun: fix LSM/SELinux labeling of tun/tap devices Paul Moore
2013-01-14 23:17 ` [PATCH 0/2] Fix some multiqueue TUN problems David Miller
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=20130114170837.31874.78897.stgit@localhost \
--to=pmoore@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).