From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Date: Wed, 2 Oct 2013 08:07:59 +0000 (+0300)
Subject: Documented order in which access rules are applied to kernel.
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2d1cb7bafdda2d03d9b581198380a37d2476acf4;p=framework%2Fsecurity%2Fsmack.git

Documented order in which access rules are applied to kernel.
(cherry picked from commit f82cadf3b7a9d84ae0bf2aa06fb8ecff9b4332dc)
---

diff --git a/libsmack/sys/smack.h b/libsmack/sys/smack.h
index 36699f0..912c769 100644
--- a/libsmack/sys/smack.h
+++ b/libsmack/sys/smack.h
@@ -75,7 +75,8 @@ void smack_accesses_free(struct smack_accesses *handle);
 int smack_accesses_save(struct smack_accesses *handle, int fd);
 
 /*!
- * Apply access rules to the kernel.
+ * Apply access rules to the kernel. Rules are applied in the order that
+ * they were added.
  *
  * @param handle handle to a struct smack_accesses instance
  * @return Returns 0 on success and negative on failure.