From 509c2d4c2f2cc311987e841423e16fa2fa3dde71 Mon Sep 17 00:00:00 2001 From: Tobias Klauser Date: Tue, 25 Sep 2007 23:57:13 +0200 Subject: inotail.c: typdef mode_t --- inotail.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'inotail.h') diff --git a/inotail.h b/inotail.h index c95c4f8..aa2a0fa 100644 --- a/inotail.h +++ b/inotail.h @@ -13,7 +13,7 @@ #define DEFAULT_N_LINES 10 /* tail modes */ -enum { M_LINES, M_BYTES }; +typedef enum { M_LINES, M_BYTES } mode_t; /* Every tailed file is represented as a file_struct */ struct file_struct { -- cgit v1.2.3-54-g00ecf t.git' title='net-next.git Git repository'/>
summaryrefslogtreecommitdiff
path: root/drivers/target/target_core_spc.c
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/target/target_core_spc.c')
d>
2011-01-17 08:05:27 -0800
commit7898e1f8e9eb1bee88c92d636e0ab93f2cbe31c6 (patch)
treed4aaa367bb42d0ff9d1e4ba227f248b5b9cd7687 /include/linux/xattr.h
parentaeda4ac3efc29e4d55989abd0a73530453aa69ba (diff)
Subject: [PATCH] Smack: mmap controls for library containment
In the embedded world there are often situations where libraries are updated from a variety of sources, for a variety of reasons, and with any number of security characteristics. These differences might include privilege required for a given library provided interface to function properly, as occurs from time to time in graphics libraries. There are also cases where it is important to limit use of libraries based on the provider of the library and the security aware application may make choices based on that criteria. These issues are addressed by providing an additional Smack label that may optionally be assigned to an object, the SMACK64MMAP attribute. An mmap operation is allowed if there is no such attribute. If there is a SMACK64MMAP attribute the mmap is permitted only if a subject with that label has all of the access permitted a subject with the current task label. Security aware applications may from time to time wish to reduce their "privilege" to avoid accidental use of privilege. One case where this arises is the environment in which multiple sources provide libraries to perform the same functions. An application may know that it should eschew services made available from a particular vendor, or of a particular version. In support of this a secondary list of Smack rules has been added that is local to the task. This list is consulted only in the case where the global list has approved access. It can only further restrict access. Unlike the global last, if no entry is found on the local list access is granted. An application can add entries to its own list by writing to /smack/load-self. The changes appear large as they involve refactoring the list handling to accomodate there being more than one rule list. Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Diffstat (limited to 'include/linux/xattr.h')