This is a note to let you know that I've just added the patch titled
audit: AUDIT_FEATURE_CHANGE message format missing delimiting space
to the 3.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
audit-audit_feature_change-message-format-missing-delimiting-space.patch
and it can be found in the queue-3.17 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 897f1acbb6702ddaa953e8d8436eee3b12016c7e Mon Sep 17 00:00:00 2001
From: Richard Guy Briggs <[email protected]>
Date: Thu, 30 Oct 2014 11:22:53 -0400
Subject: audit: AUDIT_FEATURE_CHANGE message format missing delimiting space
From: Richard Guy Briggs <[email protected]>
commit 897f1acbb6702ddaa953e8d8436eee3b12016c7e upstream.
Add a space between subj= and feature= fields to make them parsable.
Signed-off-by: Richard Guy Briggs <[email protected]>
Signed-off-by: Paul Moore <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
kernel/audit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/audit.c
+++ b/kernel/audit.c
@@ -739,7 +739,7 @@ static void audit_log_feature_change(int
ab = audit_log_start(NULL, GFP_KERNEL, AUDIT_FEATURE_CHANGE);
audit_log_task_info(ab, current);
- audit_log_format(ab, "feature=%s old=%u new=%u old_lock=%u new_lock=%u
res=%d",
+ audit_log_format(ab, " feature=%s old=%u new=%u old_lock=%u new_lock=%u
res=%d",
audit_feature_names[which], !!old_feature,
!!new_feature,
!!old_lock, !!new_lock, res);
audit_log_end(ab);
Patches currently in stable-queue which might be from [email protected] are
queue-3.17/audit-correct-audit_get_feature-return-message-type.patch
queue-3.17/audit-audit_feature_change-message-format-missing-delimiting-space.patch
queue-3.17/netlink-properly-unbind-in-error-conditions.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
