From: Paul Moore <pmoore@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: AUDIT_FEATURE_CHANGE message format missing delimiting space
Date: Thu, 30 Oct 2014 19:52:50 -0400 [thread overview]
Message-ID: <1757100.O4Ah26UjKn@sifl> (raw)
In-Reply-To: <a8618135df92d1a80814d8e4b67b09522a7b0aa8.1414682511.git.rgb@redhat.com>
On Thursday, October 30, 2014 11:22:53 AM Richard Guy Briggs wrote:
> Add a space between subj= and feature= fields to make them parsable.
>
> Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
> ---
> kernel/audit.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied to the audit stable-3.18 branch with a CC for the -stable folks. I'll
send a pull request to Linus next week, I want to wait a few days and see if
we get any other fixes for v3.18.
* git://git.infradead.org/users/pcmoore/audit stable-3.18
> diff --git a/kernel/audit.c b/kernel/audit.c
> index 53bb39b..8ee4508 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -739,7 +739,7 @@ static void audit_log_feature_change(int which, u32
> old_feature, u32 new_feature
>
> 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);
--
paul moore
security and virtualization @ redhat
prev parent reply other threads:[~2014-10-30 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 15:22 [PATCH] audit: AUDIT_FEATURE_CHANGE message format missing delimiting space Richard Guy Briggs
2014-10-30 23:52 ` Paul Moore [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1757100.O4Ah26UjKn@sifl \
--to=pmoore@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox