summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/resources/rsirq.c
diff options
context:
space:
mode:
authorJames Morris <jmorris@namei.org>2006-11-13 16:09:01 -0800
committerDavid S. Miller <davem@sunset.davemloft.net>2006-12-02 21:22:24 -0800
commit2ee92d46c6cabedd50edf6f273fa8cf84f707618 (patch)
treebdf7c64514a5063ba4ef41915f9efb6f803fc38a /drivers/acpi/resources/rsirq.c
parent90833aa4f496d69ca374af6acef7d1614c8693ff (diff)
downloadkernel-crypto-2ee92d46c6cabedd50edf6f273fa8cf84f707618.tar.gz
kernel-crypto-2ee92d46c6cabedd50edf6f273fa8cf84f707618.tar.xz
kernel-crypto-2ee92d46c6cabedd50edf6f273fa8cf84f707618.zip
[SELinux]: Add support for DCCP
This patch implements SELinux kernel support for DCCP (http://linux-net.osdl.org/index.php/DCCP), which is similar in operation to TCP in terms of connected state between peers. The SELinux support for DCCP is thus modeled on existing handling of TCP. A new DCCP socket class is introduced, to allow protocol differentation. The permissions for this class inherit all of the socket permissions, as well as the current TCP permissions (node_bind, name_bind etc). IPv4 and IPv6 are supported, although labeled networking is not, at this stage. Patches for SELinux userspace are at: http://people.redhat.com/jmorris/selinux/dccp/user/ I've performed some basic testing, and it seems to be working as expected. Adding policy support is similar to TCP, the only real difference being that it's a different protocol. Acked-by: Stephen Smalley <sds@tycho.nsa.gov> Signed-off-by: James Morris <jmorris@namei.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/acpi/resources/rsirq.c')
0 files changed, 0 insertions, 0 deletions