smack: call WARN_ONCE() instead of calling audit_log_start() 62/23262/1
authorRichard Guy Briggs <rgb@redhat.com>
Thu, 21 Nov 2013 18:57:33 +0000 (13:57 -0500)
committerRafal Krypa <r.krypa@samsung.com>
Fri, 20 Jun 2014 15:17:44 +0000 (17:17 +0200)
Remove the call to audit_log() (which call audit_log_start()) and deal with
the errors in the caller, logging only once if the condition is met.  Calling
audit_log_start() in this location makes buffer allocation and locking more
complicated in the calling tree (audit_filter_user()).

Change-Id: I318b7d926a10e9d63dfe170450345799788c6f12
Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
Signed-off-by: Eric Paris <eparis@redhat.com>
security/smack/smack_lsm.c

index 5e4ed2e188207155aef7f2e25566ffcd58592246..acd857471f957620711e24832043ca06d83fad3b 100644 (file)
@@ -3622,9 +3622,8 @@ static int smack_audit_rule_match(u32 secid, u32 field, u32 op, void *vrule,
        struct smack_known *skp;
        char *rule = vrule;
 
-       if (!rule) {
-               audit_log(actx, GFP_ATOMIC, AUDIT_SELINUX_ERR,
-                         "Smack: missing rule\n");
+       if (unlikely(!rule)) {
+               WARN_ONCE(1, "Smack: missing rule\n");
                return -ENOENT;
        }