From: Richard Guy Briggs <rgb@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
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 18:11:54 -0500 [thread overview]
Message-ID: <20140305231154.GY16640@madcap2.tricolour.ca> (raw)
In-Reply-To: <1394058876.12070.26.camel@joe-AO722>
On 14/03/05, Joe Perches wrote:
> On Wed, 2014-03-05 at 17:27 -0500, Richard Guy Briggs wrote:
> > 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.
>
> There's an unnecessary use of a \n in audit_panic too
Thanks, also queued.
> ---
> kernel/auditsc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/auditsc.c b/kernel/auditsc.c
> index 7aef2f4..da93d2e 100644
> --- a/kernel/auditsc.c
> +++ b/kernel/auditsc.c
> @@ -1157,7 +1157,7 @@ static void audit_log_execve_info(struct audit_context *context,
> */
> buf = kmalloc(MAX_EXECVE_AUDIT_LEN + 1, GFP_KERNEL);
> if (!buf) {
> - audit_panic("out of memory for argv string\n");
> + audit_panic("out of memory for argv string");
> return;
> }
>
>
>
- 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
prev parent reply other threads:[~2014-03-05 23:12 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
2014-03-05 22:34 ` Joe Perches
2014-03-05 23:11 ` Richard Guy Briggs [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=20140305231154.GY16640@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=eparis@redhat.com \
--cc=joe@perches.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®