smack: call WARN_ONCE() instead of calling audit_log_start()
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()). Signed-off-by: Richard Guy Briggs <rgb@redhat.com> Signed-off-by: Eric Paris <eparis@redhat.com>
This commit is contained in:
parent
9ad42a7924
commit
4eb0f4abfb
|
@ -3615,9 +3615,8 @@ static int smack_audit_rule_match(u32 secid, u32 field, u32 op, void *vrule,
|
||||||
struct smack_known *skp;
|
struct smack_known *skp;
|
||||||
char *rule = vrule;
|
char *rule = vrule;
|
||||||
|
|
||||||
if (!rule) {
|
if (unlikely(!rule)) {
|
||||||
audit_log(actx, GFP_ATOMIC, AUDIT_SELINUX_ERR,
|
WARN_ONCE(1, "Smack: missing rule\n");
|
||||||
"Smack: missing rule\n");
|
|
||||||
return -ENOENT;
|
return -ENOENT;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue