On Mon, Nov 17, 2014 at 02:47:32AM +0100, Karol Lewandowski wrote:
On Fri, Oct 31, 2014 at 05:36:33PM +0100, Karol Lewandowski wrote:
quoted
Signed-off-by: Karol Lewandowski <redacted>
---
drivers/misc/kdbus/bus.h | 2 ++
drivers/misc/kdbus/connection.h | 2 ++
drivers/misc/kdbus/domain.h | 2 ++
3 files changed, 6 insertions(+)
diff --git a/drivers/misc/kdbus/bus.h b/drivers/misc/kdbus/bus.h
index fd9d843..5c403ef 100644
--- a/drivers/misc/kdbus/bus.h
+++ b/drivers/misc/kdbus/bus.h
@@ -49,6 +49,7 @@
* @conn_hash: Map of connection IDs
* @monitors_list: Connections that monitor this bus
* @meta: Meta information about the bus creator
+ * @security: LSM security blob
*
* A bus provides a "bus" endpoint / device node.
*
@@ -84,6 +85,7 @@ struct kdbus_bus {
struct list_head monitors_list;
struct kdbus_meta *meta;
+ void *security;
One minor note - with possibility of LSM modules trying to access
these structures it would be worth to have kdbus headers in, say
include/linux/kdbus or similar globally accessible location.
Yes, that is a good idea.