From: Richard Guy Briggs <rgb@redhat.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Eric Paris <eparis@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] audit: remove stray newlines from audit_log_lost messages
Date: Wed, 5 Mar 2014 17:27:03 -0500 [thread overview]
Message-ID: <20140305222703.GW16640@madcap2.tricolour.ca> (raw)
In-Reply-To: <20140305212955.GV6301@hansolo.jdub.homelinux.org>
On 14/03/05, Josh Boyer wrote:
> Calling audit_log_lost with a \n in the format string leads to extra
> newlines in dmesg. That function will eventually call audit_panic which
> uses pr_err with an explicit \n included. Just make these calls match the
> others that lack \n.
>
> Reported-by: Jonathan Kamens <jik@kamens.brookline.ma.us>
> Signed-off-by: Josh Boyer <jwboyer@fedoraproject.org>
Ack. queued.
> ---
> kernel/audit.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/audit.c b/kernel/audit.c
> index 34c5a23..f6bce4d 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -396,7 +396,7 @@ static void audit_printk_skb(struct sk_buff *skb)
> if (printk_ratelimit())
> pr_notice("type=%d %s\n", nlh->nlmsg_type, data);
> else
> - audit_log_lost("printk limit exceeded\n");
> + audit_log_lost("printk limit exceeded");
> }
>
> audit_hold_skb(skb);
> @@ -412,7 +412,7 @@ static void kauditd_send_skb(struct sk_buff *skb)
> BUG_ON(err != -ECONNREFUSED); /* Shouldn't happen */
> if (audit_pid) {
> pr_err("*NO* daemon at audit_pid=%d\n", audit_pid);
> - audit_log_lost("auditd disappeared\n");
> + audit_log_lost("auditd disappeared");
> audit_pid = 0;
> audit_sock = NULL;
> }
> --
> 1.8.5.3
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2014-03-05 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 21:29 Josh Boyer
2014-03-05 22:27 ` Richard Guy Briggs [this message]
2014-03-05 22:34 ` Joe Perches
2014-03-05 23:11 ` Richard Guy Briggs
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=20140305222703.GW16640@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=eparis@redhat.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®